testcontainers-go: [Bug]: Podman - Reaper creation fails
Testcontainers version
0.14.0
Using the latest Testcontainers version?
Yes
Host OS
MacOs
Host Arch
amd64
Go Version
1.18
Docker version
podman 4.0.1
Docker info
host:
arch: amd64
buildahVersion: 1.24.1
cgroupControllers:
- memory
- pids
cgroupManager: systemd
cgroupVersion: v2
conmon:
package: conmon-2.1.0-2.fc35.x86_64
path: /usr/bin/conmon
version: 'conmon version 2.1.0, commit: '
cpus: 1
distribution:
distribution: fedora
variant: coreos
version: "35"
eventLogger: journald
hostname: localhost.localdomain
idMappings:
gidmap:
- container_id: 0
host_id: 1000
size: 1
- container_id: 1
host_id: 100000
size: 65536
uidmap:
- container_id: 0
host_id: 1000
size: 1
- container_id: 1
host_id: 100000
size: 65536
kernel: 5.15.18-200.fc35.x86_64
linkmode: dynamic
logDriver: journald
memFree: 1611247616
memTotal: 2061381632
networkBackend: netavark
ociRuntime:
name: crun
package: crun-1.4.2-1.fc35.x86_64
path: /usr/bin/crun
version: |-
crun version 1.4.2
commit: f6fbc8f840df1a414f31a60953ae514fa497c748
spec: 1.0.0
+SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +YAJL
os: linux
remoteSocket:
exists: true
path: /run/user/1000/podman/podman.sock
security:
apparmorEnabled: false
capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
rootless: true
seccompEnabled: true
seccompProfilePath: /usr/share/containers/seccomp.json
selinuxEnabled: true
serviceIsRemote: true
slirp4netns:
executable: /usr/bin/slirp4netns
package: slirp4netns-1.1.12-2.fc35.x86_64
version: |-
slirp4netns version 1.1.12
commit: 7a104a101aa3278a2152351a082a6df71f57c9a3
libslirp: 4.6.1
SLIRP_CONFIG_VERSION_MAX: 3
libseccomp: 2.5.3
swapFree: 0
swapTotal: 0
uptime: 12m 43.17s
plugins:
log:
- k8s-file
- none
- passthrough
- journald
network:
- bridge
- macvlan
volume:
- local
registries:
search:
- docker.io
store:
configFile: /var/home/core/.config/containers/storage.conf
containerStore:
number: 42
paused: 0
running: 0
stopped: 42
graphDriverName: overlay
graphOptions: {}
graphRoot: /var/home/core/.local/share/containers/storage
graphStatus:
Backing Filesystem: xfs
Native Overlay Diff: "true"
Supports d_type: "true"
Using metacopy: "false"
imageCopyTmpDir: /var/tmp
imageStore:
number: 40
runRoot: /run/user/1000/containers
volumePath: /var/home/core/.local/share/containers/storage/volumes
version:
APIVersion: 4.0.1
Built: 1645808711
BuiltTime: Fri Feb 25 19:05:11 2022
GitCommit: ""
GoVersion: go1.16.14
OsArch: linux/amd64
Version: 4.0.1
What happened?
When Skipping reaper, Podman works correctly, but when trying to create reaper getting error:
Error response from daemon: container create: statfs /var/run/docker.sock: permission denied: creating reaper failed: failed to create container
Relevant log output
Error response from daemon: container create: statfs /var/run/docker.sock: permission denied: creating reaper failed: failed to create container
Additional Information
It seems that something it missing on configuration to be able to create reaper using podman as part of this PR
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 1
- Comments: 15 (6 by maintainers)
I’m sorry, but running podman in rootful mode kind of defeats the purpose of it. This is compromising security and in no way a “solution”
fyi I found a way around to fix it for me by changing environment variables as follow:
and (sometimes?) make Podman rootful:
podman machine set --rootful;I think I figured out (by chance) what might be a/the problem and now I also understand what @fpozzobon meant with the fixed bridge network 😄 although I’m really surprised that the current test suite doesn’t cover that 😄
I’m not 100% sure if this is the only issue.
@fpozzobon did you see something like this:
when you tried running your tests?
I originally was confused by the
message. But that might also indicate that your environment is not 100% configured correctly 😅