Open riton opened 1 year ago
Apologies for the latency.. This is a weird one. Let me investigate more and see if this continues in the latest images I've built. As you say, the sticky bit is there on the tarfile, so i'm not sure why the build process is stripping it, seemingly
Description
I can't figure out why, but it looks like latest
rockylinux/rockylinux:8
androckylinux/rockylinux:9
do not have a sticky bit positionned on/tmp
.What I've observed
rockylinux/rockylinux:8 (currently pointing to
8.7
)rockylinux/rockylinux:9 (currently pointing to
9.1
)Previous behavior
The sticky bit was there in the previous minor image version
rockylinux/rockylinux:8.6
rockylinux/rockylinux:9.0
Software versions
docker version
``` ❯ docker version Client: Docker Engine - Community Version: 20.10.21 API version: 1.41 Go version: go1.18.7 Git commit: baeda1f Built: Tue Oct 25 18:01:58 2022 OS/Arch: linux/amd64 Context: default Experimental: true Server: Docker Engine - Community Engine: Version: 20.10.21 API version: 1.41 (minimum version 1.12) Go version: go1.18.7 Git commit: 3056208 Built: Tue Oct 25 17:59:49 2022 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.6.10 GitCommit: 770bd0108c32f3fb5c73ae1264f7e503fe7b2661 runc: Version: 1.1.4 GitCommit: v1.1.4-0-g5fd4c4d docker-init: Version: 0.19.0 GitCommit: de40ad0 ```O.S version
``` ❯ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy ```Kernel version
``` ❯ uname -a Linux XXXXX 5.15.0-53-generic #59-Ubuntu SMP Mon Oct 17 18:53:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ```Investigations
I've quickly looked at the various layer.tar.xz files and It seems that the sticky bit is there.
I don't really understand where it can disappear :shrug: Any help would be really appreciated.
Regards
Rémi