-
Notifications
You must be signed in to change notification settings - Fork 224
Closed
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.
Description
What happened:
It doesn't start properly.
$ kubectl get pods -A
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system kube-flannel-ds-qfmpg 0/1 Init:0/1 0 24m
kubevirt-hostpath-provisioner kubevirt-hostpath-provisioner-5jwfp 0/1 ContainerCreating 0 24m
openshift-dns dns-default-wgmmc 0/3 ContainerCreating 0 24m
openshift-ingress router-default-78d9fc46bb-xn44x 0/1 ContainerCreating 0 25m
openshift-service-ca service-ca-66bcdfc59-6j998 0/1 Pending 0 25m
What you expected to happen:
It starts
How to reproduce it (as minimally and precisely as possible):
- podman machine init
- podman machine start
- podman machine ssh
- sudo -s
- setsebool -P container_manage_cgroup true
- podman volume create ushift-vol
- podman run -d --rm --name ushift --privileged -v /lib/modules:/lib/modules -v ushift-vol:/var/lib --hostname ushift -p 6443:6443 rootfs/ushift
Anything else we need to know?:
Environment:
- Microshift version (use
microshift version): rootfs/ushift:latest - Hardware configuration:
- OS (e.g:
cat /etc/os-release): macOS with podman machine (brew install podman) - Kernel (e.g.
uname -a): Linux localhost 5.13.13-200.fc34.x86_64 Init #1 SMP Thu Aug 26 17:06:39 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux - Others: It uses Fedora CoreOS
Relevant Logs
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.