kubernetes-sigs / kubernetes-sigs/kind

[podman] Can I use kind if I change peripherals and connected devices?

Open
#2,829 4 comments 2 reactions 0 assignees View on GitHub
area/provider/podman kind/external
Dominant language
Go
Stars
15.5k
Forks
1.8k
Avg merge
1d 13h
Merged PRs (30d)
8

Description

Hello,
I encountered error which seems to be related to the fact that I often change docking station and peripherals. It seems that if I'll deploy cluster being connected to one docking station (and set of peripherals):
`KIND_EXPERIMENTAL_PROVIDER=podman kind create cluster --config=/home/lsiemiradzki/opt/kind/kind-cluster.yaml`
Then I turn it off, move to other docking station (with different set of peripherals) and try starting the main container, I'm getting:
`Error: unable to start container "containerID": error stat'ing file /dev/bus/usb/003/...`

The workaround I'm using is to throw away the control plane container and re-create the cluster. Thanks for any hints.

I checked [Known Issues](https://kind.sigs.k8s.io/docs/user/known-issues/) and [Issues] (https://github.com/kubernetes-sigs/kind/issues?q=is%3Aissue+is%3Aopen+%22Error%3A+unable+to+start+container%22), but I haven't found anything similar.

More details:
```
❯ kind --version && podman -v ; podman ps -a | grep kindest
kind version 0.14.0
podman version 3.4.2
d1b296720301 docker.io/kindest/node@sha256:0866296e693efe1fed79d5e6c7af8df71fc73ae45e3679af05342239cdc5bc8e
46 hours ago Created 0.0.0.0:8080->80/tcp, 0.0.0.0:8443->443/tcp, 127.0.0.1:36189->6443/tcp kin
d-control-plane

☸ kind-kind in ~
❯ podman start d1b296720301
Error: unable to start container "d1b29672030149cd0829fc11bfe5a1b51340cf530d00a72f112640e21bb3bd69": error stat'ing file `/
dev/bus/usb/003/007`: No such file or directory: OCI runtime attempted to invoke a command that was not found
```

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the cluster lifecycle with KIND_EXPERIMENTAL_PROVIDER=podman kind create cluster --config=/home/lsiemiradzki/opt/kind/kind-cluster.yaml, then move between docking stations and run podman start on the existing control-plane container. Compare the container's device references with the available /dev/bus/usb paths; done means determining whether an existing cluster can restart after peripherals change without recreating its control plane.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes
Domain
devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.