Closed FilBot3 closed 2 years ago
I believe also related to: https://github.com/kubernetes/minikube/issues/10737
This doesn't look like Docker at all, more like podman:
➜ ~ docker version
Version: 3.0.1
API Version: 3.0.0
Go Version: go1.15.8
Built: Fri Feb 19 10:56:17 2021
OS/Arch: linux/amd64
We should probably have some kind of warning issued, when trying to use "podman-docker".
https://github.com/containers/podman/blob/v3.0.1/docker
#!/bin/sh
[ -f /etc/containers/nodocker ] || \
echo "Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg." >&2
exec /usr/bin/podman "$@"
It is not supported in minikube, if you want to use podman you should use --driver=podman
(or alternatively, you need to install Docker [or Moby] if you want to use --driver=docker)
That little "echo" statement actually managed to segfault part of Kubernetes, that didn't expect it.
i.e. without touch /etc/containers/nodocker
and before https://github.com/containers/podman/commit/50fea69fbc017fd0da160b083780d933aa5462b5
Looking at the rest of the log, it actually did run Docker: docker version: linux-20.10.5
Problem is ! docker is currently using the btrfs storage driver
(see #7923)
Ah, I did have alias docker=podman
setup in my rc
files. Removed that an I've updated the Gist with the correct Docker version information. You're saying that the issue is the BTRFS that Fedora 33 uses though, correct?
You're saying that the issue is the BTRFS that Fedora 33 uses though, correct?
I think so, we don't have any tests for Fedora... I guess that is part of the problem.
See #3552 and the comments in other issues, such as https://github.com/kubernetes/minikube/issues/10237#issuecomment-765892917
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
On Fedora 34 now, and will try with latest Podman. Hopefully with the Docker changes, this will provide more urgency to get Podman compatibility going.
Details
Steps to reproduce the issue:
Full output of failed command:
Full log output was too large. Had to move to a Gist.
Optional: Full output of
minikube logs
command: