blocks|key|79886|text|问题是，容器中的用户作为主机上的用户具有不同的userid:groupid。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|79887|你有两种可能性：|79888|您可以确保容器中的用户与主机上的用户具有相同的userid:groupid，后者可以访问已挂载的卷。为此，您必须调整Dockerfile中的用户。在dockerfile中使用相同的userid:groupid创建一个用户，然后切换到这个用户https://docs.docker.com/engine/reference/builder/#user|ordered-list-item|offset|length|79889|您可以确保主机上的用户具有与容器中的用户相同的userid:groupid。为此，输入带有docker+exec+-it+<container-name>+bash的容器并显示用户id+id+-u+<username>组id+id+-G+<username>。将已挂载卷的权限更改为此userid:groupid。|style|CODE|79890|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.docker.com/engine/reference/builder/#user^0|0|0|3C|1I|0|0|19|11|2L|G|35|G|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@$G|X|H|Y|1|Z]]|A|$]]|$1|I|3|J|5|F|7|10|8|@$G|11|H|12|K|L]|$G|13|H|14|K|L]|$G|15|H|16|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

The problem is, that your user in the container has different userid:groupid as the user on the host.

you have two possibilities:

<ol>
<li>You can ensure that the user in the container has the same userid:groupid like the user on the host, which has access to the mounted volume. For this you have to adjust the user in the Dockerfile. Create a user in the dockerfile with the same userid:groupid and then switch to this user <a href="https://docs.docker.com/engine/reference/builder/#user" rel="noreferrer">https://docs.docker.com/engine/reference/builder/#user</a></li>
<li>You can ensure that the user on the host has the same userid:groupid like the user in the container. For this, enter the container with <code>docker exec -it &lt;container-name&gt; bash</code> and show the user id <code>id -u &lt;username&gt;</code> group id <code>id -G &lt;username&gt;</code>. Change the permissions of the mounted volume to this userid:groupid.</li>
</ol>

blocks|key|1414951|text|正如haschibaschi所述，容器中的用户与主机上的用户有不同的userid:groupid。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1414952|要解决这个问题，需要在没有(有问题的)卷映射的情况下启动容器，然后在容器上运行bash：|1414953|docker+run+-p+8080:8080+-p+50000:50000+-it+jenkins+bin/bash|code-block|syntax|javascript|1414954|一旦进入容器的shell，运行id命令，您将得到如下结果：|offset|length|style|BOLD|1414955|uid=1000(jenkins)+gid=1000(jenkins)+groups=1000(jenkins)|1414956|退出容器，转到要映射的文件夹并运行：|1414957|chown+-R+1000:1000+.|1414958|有了现在匹配的权限，您应该能够使用卷映射运行原始的docker命令。|1414959|entityMap^0|0|0|0|F|2|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|10|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|11|8|@$K|12|L|13|M|N]]|9|@]|A|$]]|$1|O|3|P|5|F|7|14|8|@]|9|@]|A|$G|H]]|$1|Q|3|R|5|6|7|15|8|@]|9|@]|A|$]]|$1|S|3|T|5|F|7|16|8|@]|9|@]|A|$G|H]]|$1|U|3|V|5|6|7|17|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|X|$]]

As haschibaschi stated your user in the container has different userid:groupid than the user on the host.

To get around this is to start the container without the (problematic) volume mapping, then run bash on the container:

<pre><code>docker run -p 8080:8080 -p 50000:50000 -it jenkins bin/bash
</code></pre>

Once inside the container's shell run the id command and you'll get results like:

<pre><code>uid=1000(jenkins) gid=1000(jenkins) groups=1000(jenkins)
</code></pre>

Exit the container, go to the folder you are trying to map and run:

<pre><code>chown -R 1000:1000 .
</code></pre>

With the permissions now matching, you should be able to run the original docker command with the volume mapping.

blocks|key|79950|text|使用以下逗号解决此错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|79951|转到您的jenkins数据挂载路径:+/media|79952|运行以下命令：|79953|cd+/media
sudo+chown+-R+ubuntu:ubuntu+sf_devops-workspaces|code-block|syntax|javascript|79954|重新启动jenkins码头集装箱|79955|docker-compose+restart+jenkins|79956|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|T|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|V|8|@]|9|@]|A|$I|J]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

This error solve using following commnad.

goto your jenkins data mount path : /media

Run following command : 

<pre><code>cd /media
sudo chown -R ubuntu:ubuntu sf_devops-workspaces
</code></pre>

restart jenkins docker container

<pre><code>docker-compose restart jenkins
</code></pre>

blocks|key|79967|text|简单地修复它以使用-u参数。请记住，这将作为根用户(uid=0)运行。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|79968|docker+run+-u+0+-d+-p+8080:8080+-p+50000:50000+-v+/data/jenkins:/var/jenkins_home+jenkins/jenkins:lts|code-block|syntax|javascript|79969|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

The easy fix it to use the -u parameter. Keep in mind this will run as a root user (uid=0)

<pre><code>docker run -u 0 -d -p 8080:8080 -p 50000:50000 -v /data/jenkins:/var/jenkins_home jenkins/jenkins:lts
</code></pre>

blocks|key|1415035|text|我有同样的问题，它被解决后，禁用SELINUX。不建议禁用SELINUX，因此请安装自定义信号模块并启用它。它起作用了。只有更改权限才能在CentOS+7上工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1415036|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had same issue it got resolved after disabling the SELINUX. 
It's not recommended to disable the SELINUX so install custom semodule and enable it. 
It works. Only changing the permissions won't work on CentOS 7.

blocks|key|79989|text|首先，您可以使用echo+$USER命令验证当前用户，然后可以在Dockerfile中提到谁是用户，就像下面这样(在我的例子中，用户是根用户)+屏幕截图|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|79990|entityMap|0|LINK|mutability|MUTABLE|url|https://i.stack.imgur.com/1hHH6.png^0|8|A|20|4|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@$9|Q|A|R|1|S]]|E|$]]|$1|F|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

first of all you can verify your current user using <code>echo $USER</code> command
and after that you can mention who is the user in the Dockerfile like bellow (in my case user is root)
<a href="https://i.stack.imgur.com/1hHH6.png" rel="nofollow noreferrer">screenshot</a>

blocks|key|1375787|text|你可能在SELinux下面。以特权身份运行容器为我解决了这个问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1375788|sudo+docker+run+--privileged+-p+8080:8080+-p+50000:50000+-v+/data/jenkins:/var/jenkins_home+jenkins/jenkins:lts|offset|length|style|CODE|1375789|来自https://docs.docker.com/engine/reference/commandline/run/#full-container-capabilities---privileged|1375790|特权标志为容器提供了所有功能，它还解除了设备cgroup控制器强制执行的所有限制。换句话说，容器可以完成主机所能做的几乎所有事情。此标志的存在是为了允许特殊的用例，例如在Docker中运行Docker。|blockquote|1375791|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.docker.com/engine/reference/commandline/run/#full-container-capabilities---privileged^0|0|0|33|0|2|2Q|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@$D|W|E|X|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|Y|8|@]|9|@$D|Z|E|10|1|11]]|A|$]]|$1|J|3|K|5|L|7|12|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

You may be under SELinux. Running the container as privileged solved the issue for me:

<code>sudo docker run --privileged -p 8080:8080 -p 50000:50000 -v /data/jenkins:/var/jenkins_home jenkins/jenkins:lts</code>

From <a href="https://docs.docker.com/engine/reference/commandline/run/#full-container-capabilities---privileged" rel="nofollow noreferrer">https://docs.docker.com/engine/reference/commandline/run/#full-container-capabilities---privileged</a>:

<blockquote>
 The --privileged flag gives all capabilities to the container, and it also lifts all the limitations enforced by the device cgroup controller. In other words, the container can then do almost everything that the host can do. This flag exists to allow special use-cases, like running Docker within Docker.
</blockquote>

blocks|key|80033|text|在MacOS上也有类似的问题，我在安装jenkins时使用helm安装了Minikube/Kubenetes，在我用来部署Jenkins的values.yaml中添加了runAsUser:+0(作为根)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|80034|master:
++usePodSecurityContext:+true
++runAsUser:+0
++fsGroup:+0|code-block|syntax|javascript|80035|只是要小心，因为这意味着您将以root用户的身份运行所有命令。|80036|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Had a similar issue on MacOS, I had installed Jenkins using helm over a Minikube/Kubenetes after many intents I fixed it adding runAsUser: 0 (as root) in the values.yaml I use to deploy jenkins.
<pre><code>master:
 usePodSecurityContext: true
 runAsUser: 0
 fsGroup: 0
</code></pre>
Just be careful because that means that you will run all your commands as root.

blocks|key|1375809|text|作为@Kiem响应的更新，使用$UID确保容器使用与主机相同的用户id，您可以这样做：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1375810|docker+run+-u+$UID+-d+-p+8080:8080+-p+50000:50000+-v+/data/jenkins:/var/jenkins_home+jenkins/jenkins:lts|code-block|syntax|javascript|1375811|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

As an update of @Kiem's response, using $UID to ensure container uses the same user id as the host, you can do this:
<pre><code>docker run -u $UID -d -p 8080:8080 -p 50000:50000 -v /data/jenkins:/var/jenkins_home jenkins/jenkins:lts
</code></pre>

blocks|key|1375836|text|我和Minikube/Kubernetes也有类似的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1375837|securityContext:
++fsGroup:+1000
++runAsUser:+0|code-block|syntax|javascript|1375838|部署->规范->模板->规范|1375839|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I had a similar issue with Minikube/Kubernetes just added
<pre><code>securityContext:
 fsGroup: 1000
 runAsUser: 0
</code></pre>
under deployment -&gt; spec -&gt; template -&gt; spec

I have a virtual machine hosting Oracle Linux where I've installed Docker and created containers using a docker-compose file. I placed the jenkins volume under a shared folder but when starting the docker-compose up I got the following error for Jenkins :

<blockquote>
 jenkins | touch: cannot touch ‘/var/jenkins_home/copy_reference_file.log’: Permission denied
 jenkins | Can not write to /var/jenkins_home/copy_reference_file.log. Wrong volume permissions?
 jenkins exited with code 1
</blockquote>

Here's the volumes declaration

<pre><code> volumes:
 - "/media/sf_devops-workspaces/dev-tools/continuous-integration/jenkins:/var/jenkins_home"
</code></pre>

Jenkins wrong volume permissions

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有一个托管Oracle Linux的虚拟机，在这里我安装了Docker，并使用docker-compose文件创建了容器。我将jenkins卷放在一个共享文件夹下，但是当启动docker时，我得到了Jenkins的以下错误：jenkins _ touch:无法触摸‘/var/ jenkins _home/copy_r...

问Jenkins错误的卷权限
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Jenkins错误的卷权限EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Jenkins错误的卷权限
EN