ekarlso
commented
2 years ago I think I am hitting the same issues on Ubuntu too.
Open BrentFathom5 opened 2 years ago
ekarlso
commented
2 years ago I think I am hitting the same issues on Ubuntu too.
Cubxity
commented
2 years ago The same issue is reproducable on Fedora Workstation 36
idlefella
commented
2 years ago I have the same issue on rhel8 when I try to use rootless podman with the following versions:
I intercepted the call from k3d to podman with socat and found the following request which fails:
{
"Hostname": "k3d-mlp-tools",
"Domainname": "",
"User": "",
"AttachStdin": false,
"AttachStdout": false,
"AttachStderr": false,
"Tty": false,
"OpenStdin": false,
"StdinOnce": false,
"Env": [
"K3S_KUBECONFIG_OUTPUT=/output/kubeconfig.yaml"
],
"Cmd": [
"noop"
],
"Image": "ghcr.io/k3d-io/k3d-tools:5.4.6",
"Volumes": null,
"WorkingDir": "",
"Entrypoint": null,
"OnBuild": null,
"Labels": {
"app": "k3d",
"k3d.cluster": "mlp",
"k3d.role": "noRole",
"k3d.version": "v5.4.6"
},
"HostConfig": {
"Binds": [
"k3d-mlp-images:/k3d/images",
"unix:///run/user/2625/podman/podman2.sock:unix:///run/user/2625/podman/podman2.sock"
],
"ContainerIDFile": "",
"LogConfig": {
"Type": "",
"Config": null
},
"NetworkMode": "bridge",
"PortBindings": null,
"RestartPolicy": {
"Name": "",
"MaximumRetryCount": 0
},
"AutoRemove": false,
"VolumeDriver": "",
"VolumesFrom": null,
"CapAdd": null,
"CapDrop": null,
"CgroupnsMode": "",
"Dns": null,
"DnsOptions": null,
"DnsSearch": null,
"ExtraHosts": [
"host.k3d.internal:host-gateway"
],
"GroupAdd": null,
"IpcMode": "",
"Cgroup": "",
"Links": null,
"OomScoreAdj": 0,
"PidMode": "",
"Privileged": true,
"PublishAllPorts": false,
"ReadonlyRootfs": false,
"SecurityOpt": null,
"Tmpfs": {
"/run": "",
"/var/run": ""
},
"UTSMode": "",
"UsernsMode": "",
"ShmSize": 0,
"ConsoleSize": [
0,
0
],
"Isolation": "",
"CpuShares": 0,
"Memory": 0,
"NanoCpus": 0,
"CgroupParent": "",
"BlkioWeight": 0,
"BlkioWeightDevice": null,
"BlkioDeviceReadBps": null,
"BlkioDeviceWriteBps": null,
"BlkioDeviceReadIOps": null,
"BlkioDeviceWriteIOps": null,
"CpuPeriod": 0,
"CpuQuota": 0,
"CpuRealtimePeriod": 0,
"CpuRealtimeRuntime": 0,
"CpusetCpus": "",
"CpusetMems": "",
"Devices": null,
"DeviceCgroupRules": null,
"DeviceRequests": null,
"KernelMemory": 0,
"KernelMemoryTCP": 0,
"MemoryReservation": 0,
"MemorySwap": 0,
"MemorySwappiness": null,
"OomKillDisable": null,
"PidsLimit": null,
"Ulimits": null,
"CpuCount": 0,
"CpuPercent": 0,
"IOMaximumIOps": 0,
"IOMaximumBandwidth": 0,
"MaskedPaths": null,
"ReadonlyPaths": null,
"Init": true
},
"NetworkingConfig": {
"EndpointsConfig": {
"k3d-mlp": {
"IPAMConfig": null,
"Links": null,
"Aliases": null,
"NetworkID": "",
"EndpointID": "",
"Gateway": "",
"IPAddress": "",
"IPPrefixLen": 0,
"IPv6Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"MacAddress": "",
"DriverOpts": null
}
}
}
}The response:
{
"cause": "incorrect volume format, should be [host-dir:]ctr-dir[:option]",
"message": "fill out specgen: unix:///run/user/2625/podman/podman2.sock:unix:///run/user/2625/podman/podman2.sock: incorrect volume format, should be [host-dir:]ctr-dir[:option]",
"response": 500
}The problem seems to be that Volumes doesn't have the correct format. In the request it is null...
idlefella
commented
2 years ago The error came because I've set the environment variable DOCKER_SOCK=unix://... (starting with unix://) The following option worked for me, but I later ran into another issue:
DOCKER_SOCK=$XDG_RUNTIME_DIR/podman/podman.sock
DOCKER_HOST=unix://$XDG_RUNTIME_DIR/podman/podman.sock
testdruid
commented
1 year ago I ran into the same issue on a RHEL 8 setup with latest versions.
What did you do The commands here: https://k3d.io/v5.4.9/usage/advanced/podman/?h=podman#using-podman
Screenshots or terminal output
INFO[0000] Prep: Network
INFO[0000] Created network 'k3d-k3s-default'
INFO[0000] Created image volume k3d-k3s-default-images
INFO[0000] Starting new tools node...
INFO[0000] Starting Node 'k3d-k3s-default-tools'
INFO[0001] Creating node 'k3d-k3s-default-server-0'
INFO[0001] Creating LoadBalancer 'k3d-k3s-default-serverlb'
INFO[0001] Using the k3d-tools node to gather environment information
INFO[0001] HostIP: using network gateway 10.89.0.1 address
INFO[0001] Starting cluster 'k3s-default'
INFO[0001] Starting servers...
INFO[0001] Starting Node 'k3d-k3s-default-server-0'
INFO[0006] All agents already running.
INFO[0006] Starting helpers...
INFO[0007] Starting Node 'k3d-k3s-default-serverlb'
ERRO[0018] Failed Cluster Start: Failed to add one or more helper nodes: Node k3d-k3s-default-serverlb failed to get ready: error waiting for log line start worker processes from node 'k3d-k3s-default-serverlb': stopped returning log lines: node k3d-k3s-default-serverlb is running=true in status=running
ERRO[0018] Failed to create cluster >>> Rolling Back
INFO[0018] Deleting cluster 'k3s-default'
INFO[0019] Deleting cluster network 'k3d-k3s-default'
INFO[0019] Deleting 2 attached volumes...
WARN[0019] Failed to delete volume 'k3d-k3s-default-images' of cluster 'k3s-default': failed to find volume 'k3d-k3s-default-images': Error: No such volume: k3d-k3s-default-images -> Try to delete it manually
FATA[0019] Cluster creation FAILED, all changes have been rolled back!
Versions $ cat /etc/redhat-release Red Hat Enterprise Linux release 8.3 (Ootpa) $ k3d --version k3d version v5.4.6 k3s version v1.24.4-k3s1 (default) $ podman --version podman version 4.2.0
jonahbrawley
commented
1 year ago Running into the same error as @testdruid. I've tried following the docs on k3d's site to setup for use with podman, and have also tried clean reinstalling. Podman service is running, and I've made a symlink with the instructions on the previously mentioned docs.
Versions: $ podman --version
podman version 4.0.2
$ k3d --version
k3d version v5.5.1 k3s version v1.26.4-k3s1 (default)
$ cat /etc/redhat-release
Red Hat Enterprise Linux release 8.7 (Ootpa)
Logs: $ sudo $(which k3d) cluster create mycluster
INFO[0000] Prep: Network
INFO[0000] Re-using existing network 'k3d-mycluster' (123f6c30a3b584f5192b402e975a4d4e5a95716c4be505eb92b5023a782c38de)
INFO[0000] Created image volume k3d-mycluster-images
INFO[0000] Starting new tools node...
INFO[0000] Starting Node 'k3d-mycluster-tools'
INFO[0001] Creating node 'k3d-mycluster-server-0'
INFO[0001] Creating LoadBalancer 'k3d-mycluster-serverlb'
INFO[0001] Using the k3d-tools node to gather environment information
INFO[0001] HostIP: using network gateway 10.89.1.1 address
INFO[0001] Starting cluster 'mycluster'
INFO[0001] Starting servers...
INFO[0001] Starting Node 'k3d-mycluster-server-0'
INFO[0004] All agents already running.
INFO[0004] Starting helpers...
INFO[0004] Starting Node 'k3d-mycluster-serverlb'
ERRO[0011] Failed Cluster Start: Failed to add one or more helper nodes: Node k3d-mycluster-serverlb failed to get ready: error waiting for log line `start worker processes` from node 'k3d-mycluster-serverlb': stopped returning log lines: node k3d-mycluster-serverlb is running=true in status=running
ERRO[0011] Failed to create cluster >>> Rolling Back
INFO[0011] Deleting cluster 'mycluster'
INFO[0012] Deleting 1 attached volumes...
FATA[0012] Cluster creation FAILED, all changes have been rolled back!
gedw99
commented
1 year ago ah me too :) on mac
spectdecomp
commented
8 months ago Running into the same error as @testdruid. I've tried following the docs on k3d's site to setup for use with podman, and have also tried clean reinstalling. Podman service is running, and I've made a symlink with the instructions on the previously mentioned docs.
Versions: $ podman --version
podman version 4.0.2
$ k3d --version
k3d version v5.5.1 k3s version v1.26.4-k3s1 (default)
$ cat /etc/redhat-release
Red Hat Enterprise Linux release 8.7 (Ootpa)
Logs: $ sudo $(which k3d) cluster create mycluster
INFO[0000] Prep: Network INFO[0000] Re-using existing network 'k3d-mycluster' (123f6c30a3b584f5192b402e975a4d4e5a95716c4be505eb92b5023a782c38de) INFO[0000] Created image volume k3d-mycluster-images INFO[0000] Starting new tools node... INFO[0000] Starting Node 'k3d-mycluster-tools' INFO[0001] Creating node 'k3d-mycluster-server-0' INFO[0001] Creating LoadBalancer 'k3d-mycluster-serverlb' INFO[0001] Using the k3d-tools node to gather environment information INFO[0001] HostIP: using network gateway 10.89.1.1 address INFO[0001] Starting cluster 'mycluster' INFO[0001] Starting servers... INFO[0001] Starting Node 'k3d-mycluster-server-0' INFO[0004] All agents already running. INFO[0004] Starting helpers... INFO[0004] Starting Node 'k3d-mycluster-serverlb' ERRO[0011] Failed Cluster Start: Failed to add one or more helper nodes: Node k3d-mycluster-serverlb failed to get ready: error waiting for log line `start worker processes` from node 'k3d-mycluster-serverlb': stopped returning log lines: node k3d-mycluster-serverlb is running=true in status=running ERRO[0011] Failed to create cluster >>> Rolling Back INFO[0011] Deleting cluster 'mycluster' INFO[0012] Deleting 1 attached volumes... FATA[0012] Cluster creation FAILED, all changes have been rolled back!The exact same error message appeared. More than six months have passed and the issue is still unresolved.
What did you do
k3d cluster create --verboseScreenshots or terminal output
Here is the resulting terminal output:
I can verify that the Podman service is up and running as well by running
systemctl status podman:Which OS & Architecture
Output of
k3d runtime-info:I'm also setting the following environment variables in my
~/.zshrcfile:Which version of
k3dOutput of
k3d version:Which version of docker
Output of
docker version:Output of
docker info: