Ask questionsFully specify image sources
<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!-->
$ kind create cluster enabling experimental podman provider Creating cluster "kind" ... ✗ Ensuring node image (kindest/node:v1.20.2) 🖼 ERROR: failed to create cluster: failed to pull image "kindest/node@sha256:8f7ea6e7642c0da54f04a7ee10431549c0257315b3a634f6ef2fecaaedb19bab": command "podman pull kindest/node@sha256:8f7ea6e7642c0da54f04a7ee10431549c0257315b3a634f6ef2fecaaedb19bab" failed with error: exit status 125 Command Output: Error: error getting default registries to try: short-name resolution enforced but cannot prompt without a TTY
What you expected to happen:
kind create cluster enabling experimental podman provider Creating cluster "kind" ... ✓ Ensuring node image (kindest/node:v1.20.2) 🖼 ✓ Preparing nodes 📦 ✓ Writing configuration 📜 ✓ Starting control-plane 🕹️ ✓ Installing CNI 🔌 ✓ Installing StorageClass 💾 Set kubectl context to "kind-kind" You can now use your cluster with: kubectl cluster-info --context kind-kind Have a nice day! 👋
How to reproduce it (as minimally and precisely as possible):
Use a distro with >=Podman 3.0 with
short-name-mode="enforcing" enabled in
kind as per the documentation. Try to create a cluster.
Anything else we need to know?:
Container short name mode for Podman has been set to
enforcing by default for Fedora 34 and newer. This brakes the current scripts.
To fix this you can set the setting to
short-name-mode="permissive". This should be added to the known issues page.
As a more robust fix,
kind should fully specify image sources in its scripts.
kind v0.10.0 go1.15.7 linux/amd64
kubectl version): N/A
docker info): Podman
/etc/os-release): Fedora IoT 34 Beta
Answer questions aojea
short-name-mode="permissive"as suggested above.
@vrothberg is there a way to set permissive using podman flags or environment variables?