podman: substituting podman for docker for use with kubernetes kind fails
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Trying to substitute the requirement for docker in the kind (kubernetes in docker) tool https://github.com/kubernetes-sigs/kind, and it fails due to the combination of arguments that podman is launched with.
Steps to reproduce the issue:
-
Download / install kind (put it in your path and chmod +x the binary)
-
Create a symlink for docker to point to podman (ln -s /usr/bin/podman ~/bin/docker)
-
Try to create a cluster ‘kind create cluster’
Describe the results you received: The tool launches podman (thinking that it is really docker) with a combination of flags that causes podman to error.
jdiaz@minigoomba ~]$ kind create cluster --loglevel=debug
DEBU[16:20:06] Running: /home/jdiaz/bin/docker [docker ps -q -a --no-trunc --filter label=io.k8s.sigs.kind.cluster --format {{.Names}}\t{{.Label "io.k8s.sigs.kin
d.cluster"}}]
Error: could not list clusters: failed to list nodes: exit status 125
Describe the results you expected: Would like podman to accept the same set of CLI parameters as docker.
Additional information you deem important (e.g. issue happens only occasionally): When actually running the command that ‘kind’ invokes you get this output:
[jdiaz@minigoomba ~]$ docker ps -q -a --no-trunc --filter label=io.k8s.sigs.kind.cluster --format '{{.Names}}\t{{.Label "io.k8s.sigs.kind.cluster"}}'
Error: error with flags passed: quiet conflicts with size, namespace, and format with go template
Output of podman version:
[jdiaz@minigoomba ~]$ podman version
Version: 1.6.2
RemoteAPI Version: 1
Go Version: go1.13.1
OS/Arch: linux/amd64
Output of podman info --debug:
[jdiaz@minigoomba ~]$ podman info --debug
debug:
compiler: gc
git commit: ""
go version: go1.13.1
podman version: 1.6.2
host:
BuildahVersion: 1.11.3
CgroupVersion: v2
Conmon:
package: conmon-2.0.2-1.fc31.x86_64
path: /usr/bin/conmon
version: 'conmon version 2.0.2, commit: 186a550ba0866ce799d74006dab97969a2107979'
Distribution:
distribution: fedora
version: "31"
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
MemFree: 8088338432
MemTotal: 16664195072
OCIRuntime:
name: crun
package: crun-0.10.2-1.fc31.x86_64
path: /usr/bin/crun
version: |-
crun version 0.10.2
spec: 1.0.0
+SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +YAJL
SwapFree: 7983435776
SwapTotal: 8401186816
arch: amd64
cpus: 8
eventlogger: journald
hostname: minigoomba
kernel: 5.3.7-301.fc31.x86_64
os: linux
rootless: true
slirp4netns:
Executable: /usr/bin/slirp4netns
Package: slirp4netns-0.4.0-20.1.dev.gitbbd6f25.fc31.x86_64
Version: |-
slirp4netns version 0.4.0-beta.3+dev
commit: bbd6f25c70d5db2a1cd3bfb0416a8db99a75ed7e
uptime: 121h 9m 15.68s (Approximately 5.04 days)
registries:
blocked: null
insecure: null
search:
- docker.io
- registry.fedoraproject.org
- quay.io
- registry.access.redhat.com
- registry.centos.org
store:
ConfigFile: /home/jdiaz/.config/containers/storage.conf
ContainerStore:
number: 0
GraphDriverName: overlay
GraphOptions:
overlay.mount_program:
Executable: /usr/bin/fuse-overlayfs
Package: fuse-overlayfs-0.6.5-2.fc31.x86_64
Version: |-
fusermount3 version: 3.6.2
fuse-overlayfs: version 0.6.5
FUSE library version 3.6.2
using FUSE kernel interface version 7.29
GraphRoot: /home/jdiaz/.local/share/containers/storage
GraphStatus:
Backing Filesystem: extfs
Native Overlay Diff: "false"
Supports d_type: "true"
Using metacopy: "false"
ImageStore:
number: 6
RunRoot: /run/user/1000
VolumePath: /home/jdiaz/.local/share/containers/storage/volumes
Package info (e.g. output of rpm -q podman or apt list podman):
[jdiaz@minigoomba ~]$ rpm -q podman
podman-1.6.2-2.fc31.x86_64
Additional environment details (AWS, VirtualBox, physical, etc.): Fedora 31 system on a physical machine.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 1
- Comments: 17 (9 by maintainers)
Just for the reference, KinD does not work with podman. There are many small things need to be addressed in KinD project to make it work properly.
I’ll take this one