Package: docker
Version: 1.5-2
Severity: minor

Dear Maintainer,

When trying to execute docker manifest (on a custom registry) for example:
`DOCKER_CLI_EXPERIMENTAL=enabled docker manifest inspect --verbose
registry.gitlab.com/neroburner/manifest-test/amd64/ubuntu:bionic` (not my repo,
pulled from a gitlab bug report ;)

we get the following error:

"open /etc/docker/certs.d/registry.gitlab.com: permission denied"

Not sure why I am getting this error, as I can find very little information
online.

Doing a `sudo chroot +X /etc/docker` resolves this issues completly.

Looking at other systems, gentoo, we get the same state, with the same fix
working.

Interestingly however, that on alpine, where the entire directory does not even
exist (with my test running a docker container of alpine where I only did apk
add and added a user) does not suffer from this problem. So at the least,
giving directory traversal access means docker can at least work.



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 5.6.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages docker depends on:
ii  wmdocker  1.5-2

docker recommends no packages.

docker suggests no packages.

-- no debconf information

  • Bug#969002: docker-manifest needs executable access to /e... Olliver Schinagl

Reply via email to