-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running containers with podman doesn't work #4406
Labels
co/runtime/crio
CRIO related issues
kind/bug
Categorizes issue or PR as related to a bug.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
Milestone
Comments
afbjorklund
added
kind/bug
Categorizes issue or PR as related to a bug.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
co/runtime/crio
CRIO related issues
labels
Jun 2, 2019
Similar to cri-o/cri-o#1423 |
Our current CNI configuration lives at: /etc/cni/net.d/k8s.conf {
"name": "rkt.kubernetes.io",
"type": "bridge",
"bridge": "mybridge",
"mtu": 1460,
"addIf": "true",
"isGateway": true,
"ipMasq": true,
"ipam": {
"type": "host-local",
"subnet": "10.1.0.0/16",
"gateway": "10.1.0.1",
"routes": [
{
"dst": "0.0.0.0/0"
}
]
}
} |
Here is the example configuration, from podman v1.3.1: {
"cniVersion": "0.3.0",
"name": "podman",
"plugins": [
{
"type": "bridge",
"bridge": "cni0",
"isGateway": true,
"ipMasq": true,
"ipam": {
"type": "host-local",
"subnet": "10.88.0.0/16",
"routes": [
{ "dst": "0.0.0.0/0" }
]
}
},
{
"type": "portmap",
"capabilities": {
"portMappings": true
}
}
]
} So it seems we should upgrade ours to cniVersion 0.3.0 |
There are some other changes needed as well:
$ sudo podman run -it busybox
Error: write child: broken pipe
$ sudo podman run -it busybox
Error: container create failed: systemd cgroup flag passed, but systemd support for managing cgroups is not available
$ sudo podman run -it busybox
Error: container create failed: container_linux.go:345: starting container process caused "process_linux.go:424: container init caused \"rootfs_linux.go:109: jailing process inside rootfs caused \\\"pivot_root invalid argument\\\"\"" But after those four fixes, it works as intended. |
afbjorklund
changed the title
Running containers with podman doesn't work (CNI)
Running containers with podman doesn't work
Jun 2, 2019
Needs #4421 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
co/runtime/crio
CRIO related issues
kind/bug
Categorizes issue or PR as related to a bug.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
We install the
podman
tool into the VM, to do things such as loading or building OCI images.But currently there are some issues with the CNI configuration, if you try to use it for running:
Even though it is not the primary use-case (normally use crictl/crio), this should work...
Maybe we can get the standard minikube CNI configuration compatible with Podman ?
The text was updated successfully, but these errors were encountered: