Closed AkihiroSuda closed 3 years ago
coredns doesn't start up with CRI-O, though it can start up with containerd
...
containerStatuses:
- image: coredns/coredns:1.6.9
imageID: ""
lastState: {}
name: coredns
ready: false
restartCount: 0
started: false
state:
waiting:
message: |
container create failed: time="2020-09-02T19:26:04+09:00" level=warning msg="exit status 1"
time="2020-09-02T19:26:04+09:00" level=error msg="container_linux.go:370: starting container process caused: process_linux.go:459: container init caused: rootfs_linux.go:60: mounting \"/run/user/1001/usernetes/containers/storage/overlay-containers/dad49321dc8b57d4bc65665972bfaccf3a6be9416ed05c0a02cdc98be1ed603b/userdata/hostname\" to rootfs at \"/home/suda/.local/share/usernetes/containers/storage/overlay/9986c016a134d19deffa4793dc57d4036e1362605658260212625cd1baa8ddec/merged/etc/hostname\" caused: operation not permitted"
reason: CreateContainerError
cc @giuseppe
runc should have matured enough to support cgroup v2 now