moby: permissions broken after chown in overlay2
Similar to this #20240 and #24913 but overlay2 instead of aufs
and overlay
.
Output of docker version
:
Client:
Version: 1.12.3
API version: 1.24
Go version: go1.6.3
Git commit: 6b644ec
Built: Wed Oct 26 21:44:32 2016
OS/Arch: linux/amd64
Server:
Version: 1.12.3
API version: 1.24
Go version: go1.6.3
Git commit: 6b644ec
Built: Wed Oct 26 21:44:32 2016
OS/Arch: linux/amd64
Output of docker info
:
Containers: 6
Running: 6
Paused: 0
Stopped: 0
Images: 18
Server Version: 1.12.3
Storage Driver: overlay2
Backing Filesystem: extfs
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: apparmor
Kernel Version: 4.4.0-47-generic
Operating System: Ubuntu 14.04.5 LTS
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 23.48 GiB
Name: aam-inv-tb1
ID: Q7SH:ZX2R:YBQB:S5O6:327O:XBYL:G2MI:JS52:7XJ6:7TMH:ATBE:6BNT
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Insecure Registries:
registry:5000
127.0.0.0/8
Output of uname -a
$ uname -a
Linux aam-inv-tb1 4.4.0-47-generic #68~14.04.1-Ubuntu SMP Wed Oct 26 19:42:11 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Additional environment details (AWS, VirtualBox, physical, etc.):
physical machine running Ubuntu 14.04
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 33 (15 by maintainers)
Commits related to this issue
- Add overlay2 issue docker/docker#28391 (resolved) — committed to AkihiroSuda/issues-docker by AkihiroSuda 8 years ago
- bionic-jenkins-slave image support Ubuntu 18.04 is significantly newer. In particular, we're hoping that the kernel available there will give us fewer issues with docker overlay support, as observed ... — committed to cybera/jenkins-images by deleted user 5 years ago
@snth we require a bug in launchpad for any changes to stable releases. I went ahead and created a bug:
http://bugs.launchpad.net/bugs/1659417
Our release process requires that our release candidate kernels be tested before release to verify that the bug is fixed. I’ll post back here at that point to request testing, which should be 2-3 weeks from now.
For the original issue of which reproduction procedure is described at https://github.com/docker/docker/issues/28391#issuecomment-260642494, I cannot hit the issue with 38b78a5, but can hit with the previous commit 3c9fe8cd .
(For this bisecting, I used https://github.com/AkihiroSuda/latest-docker-on-latest-kernel/tree/v0.1 . e.g.
ldlk --kernel-version 38b78a5 --docker-version v1.13.0-rc2 tmp01
)So I believe the original issue was resolved in 38b78a5, and suggest closing this issue.
PTAL @dmcgowan
@andrewmichaelsmith Please open another issue?