[BUG] Unable to create registry, network not found #1162
Description
What did you do
Trying to create a registry, either with k3d reg create or k3d cluster create --registry-create results in the following error:
FATA[0000] Failed to create registry: failed to create registry node 'k3d-registry': runtime failed to create node 'k3d-registry': failed to create container for node 'k3d-registry': docker failed to create container 'k3d-registry': Error response from daemon: container create: unable to find network with name or ID bridge: network not found
I tried rebooting, uninstalling docker, podman and k3d, only installing podman and k3d to no avail. I'm using a rootful podman VM (podman machine init -v $HOME:$HOME --rootful)
Using --verbose does not give much information:
k3d reg create --verbose
DEBU[0000] DOCKER_SOCK=/var/run/docker.sock
DEBU[0000] Runtime Info:
&{Name:docker Endpoint:/var/run/docker.sock Version:4.2.0 OSType:linux OS:fedora Arch:arm64 CgroupVersion:2 CgroupDriver:systemd Filesystem:xfs}
DEBU[0000] Port Exposure Mapping didn't specify hostPort, choosing one randomly...
DEBU[0000] Got free port for Port Exposure: '50275'
INFO[0000] Creating node 'k3d-registry'
DEBU[0000] DOCKER_SOCK=/var/run/docker.sock
DEBU[0000] Detected CgroupV2, enabling custom entrypoint (disable by setting K3D_FIX_CGROUPV2=false)
FATA[0000] Failed to create registry: failed to create registry node 'k3d-registry': runtime failed to create node 'k3d-registry': failed to create container for node 'k3d-registry': docker failed to create container 'k3d-registry': Error response from daemon: container create: unable to find network with name or ID bridge: network not found
Which OS & Architecture
This is on a Mac M1
- output of
k3d runtime-info
arch: arm64
cgroupdriver: systemd
cgroupversion: "2"
endpoint: /var/run/docker.sock
filesystem: xfs
name: docker
os: fedora
ostype: linux
version: 4.2.0
Which version of k3d
- output of
k3d version
k3d version v5.4.6
k3s version v1.24.4-k3s1 (default)
Which version of docker
I'm using podman (docker being an alias of podman)
- output of
docker version
Client: Podman Engine
Version: 4.2.1
API Version: 4.2.1
Go Version: go1.18.6
Built: Tue Sep 6 15:16:02 2022
OS/Arch: darwin/arm64
Server: Podman Engine
Version: 4.2.0
API Version: 4.2.0
Go Version: go1.18.4
Built: Thu Aug 11 10:43:11 2022
OS/Arch: linux/arm64
docker info
host:
arch: arm64
buildahVersion: 1.27.0
cgroupControllers:
- cpuset
- cpu
- io
- memory
- pids
- misc
cgroupManager: systemd
cgroupVersion: v2
conmon:
package: conmon-2.1.4-2.fc36.aarch64
path: /usr/bin/conmon
version: 'conmon version 2.1.4, commit: '
cpuUtilization:
idlePercent: 96.5
systemPercent: 2.45
userPercent: 1.05
cpus: 1
distribution:
distribution: fedora
variant: coreos
version: "36"
eventLogger: journald
hostname: localhost.localdomain
idMappings:
gidmap: null
uidmap: null
kernel: 5.19.9-200.fc36.aarch64
linkmode: dynamic
logDriver: journald
memFree: 1288761344
memTotal: 2051575808
networkBackend: netavark
ociRuntime:
name: crun
package: crun-1.6-2.fc36.aarch64
path: /usr/bin/crun
version: |-
crun version 1.6
commit: 18cf2efbb8feb2b2f20e316520e0fd0b6c41ef4d
spec: 1.0.0
+SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +YAJL
os: linux
remoteSocket:
exists: true
path: /run/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: false
seccompEnabled: true
seccompProfilePath: /usr/share/containers/seccomp.json
selinuxEnabled: true
serviceIsRemote: true
slirp4netns:
executable: /usr/bin/slirp4netns
package: slirp4netns-1.2.0-0.2.beta.0.fc36.aarch64
version: |-
slirp4netns version 1.2.0-beta.0
commit: 477db14a24ff1a3de3a705e51ca2c4c1fe3dda64
libslirp: 4.6.1
SLIRP_CONFIG_VERSION_MAX: 3
libseccomp: 2.5.3
swapFree: 0
swapTotal: 0
uptime: 0h 10m 7.00s
plugins:
authorization: null
log:
- k8s-file
- none
- passthrough
- journald
network:
- bridge
- macvlan
volume:
- local
registries:
search:
- docker.io
store:
configFile: /usr/share/containers/storage.conf
containerStore:
number: 0
paused: 0
running: 0
stopped: 0
graphDriverName: overlay
graphOptions:
overlay.mountopt: nodev,metacopy=on
graphRoot: /var/lib/containers/storage
graphRootAllocated: 106825756672
graphRootUsed: 2327588864
graphStatus:
Backing Filesystem: xfs
Native Overlay Diff: "false"
Supports d_type: "true"
Using metacopy: "true"
imageCopyTmpDir: /var/tmp
imageStore:
number: 1
runRoot: /run/containers/storage
volumePath: /var/lib/containers/storage/volumes
version:
APIVersion: 4.2.0
Built: 1660228991
BuiltTime: Thu Aug 11 10:43:11 2022
GitCommit: ""
GoVersion: go1.18.4
Os: linux
OsArch: linux/arm64
Version: 4.2.0
docker network ls
NETWORK ID NAME DRIVER
2f259bab93aa podman bridge
For what it's worth, I uninstalled podman and used docker-desktop, and now k3d reg create completed successfully.