k3s 1.18.8 pods stuck in CrashLoopBackOff

Environmental Info:
K3s Version:
[root@fox ~]# ./k3s -v
k3s version v1.18.8+k3s1 (6b595318)

Node(s) CPU architecture, OS, and Version:

[root@fox ~]# cat /etc/centos-release
CentOS Linux release 7.8.2003 (Core)

[root@fox ~]# uname -a
Linux fox 3.10.0-1127.el7.x86_64 rancher/k3s#1 SMP Tue Mar 31 23:36:51 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Cluster Configuration:

1 server functioning as master and node
Describe the bug:

When running k3s server all pods will stay in CrashLoopBackOff.
[root@fox ~]# ./k3s kubectl get pods --all-namespaces
NAMESPACE     NAME                                     READY   STATUS             RESTARTS   AGE
kube-system   local-path-provisioner-6d59f47c7-ff9bg   0/1     CrashLoopBackOff   15         51m
kube-system   helm-install-traefik-mg6lk               0/1     CrashLoopBackOff   13         51m
kube-system   coredns-7944c66d8d-zgkzs                 0/1     CrashLoopBackOff   15         51m
kube-system   metrics-server-7566d596c8-fks6z          0/1     CrashLoopBackOff   14         51m

[root@fox ~]# ./k3s kubectl logs -n kube-system coredns-7944c66d8d-zgkzs
failed to try resolving symlinks in path "/var/log/pods/kube-system_coredns-7944c66d8d-zgkzs_ba5156ce-3f67-4773-8335-d0119089f340/coredns/15.log": lstat /var/log/pods/kube-system_coredns-7944c66d8d-zgkzs_ba5156ce-3f67-4773-8335-d0119089f340/coredns/15.log: no such file or directory

The error message seems to be related to the fact that no '*.log' file is created. However the directory does exist.
[root@fox ~]# ls -l /var/log/pods/kube-system_coredns-7944c66d8d-zgkzs_ba5156ce-3f67-4773-8335-d0119089f340/coredns/
total 0

Steps To Reproduce:

Install clean CentOS 7
Install k3s

$ wget https://github.com/rancher/k3s/releases/download/v1.18.8%2Bk3s1/k3s

Run k3s

./k3s server

Verify status of pods

[root@fox ~]# ./k3s kubectl get pods -n kube-system
NAME                                     READY   STATUS             RESTARTS   AGE
helm-install-traefik-mg6lk               0/1     CrashLoopBackOff   14         57m
metrics-server-7566d596c8-fks6z          0/1     CrashLoopBackOff   15         57m
local-path-provisioner-6d59f47c7-ff9bg   0/1     CrashLoopBackOff   16         57m
coredns-7944c66d8d-zgkzs                 0/1     CrashLoopBackOff   16         57m

Expected behavior:

I would expect the pods to be in a Running state.
Actual behavior:

The pods are in a CrashLoopBackOff state and are contstantly restarting.
The log files of the pods specify the following
lstat /var/log/pods/kube-system_coredns-7944c66d8d-zgkzs_ba5156ce-3f67-4773-8335-d0119089f340/coredns/15.log: no such file or directory

After some retries the file is created and no error mesage is shown anymore, however the pod is still in CrashLoopBackOff status.
# File has been created
[root@fox ~]# ls -l /var/log/pods/kube-system_coredns-7944c66d8d-zgkzs_ba5156ce-3f67-4773-8335-d0119089f340/coredns/
total 0
-rw-r-----. 1 root root 0 Aug 24 16:09 16.log

# No logs are shown
[root@fox ~]# ./k3s  kubectl logs -n kube-system coredns-7944c66d8d-zgkzs

# Pods are still in CrashLoopBackOff status
[root@fox ~]# ./k3s kubectl get pods -n kube-system
NAME                                     READY   STATUS             RESTARTS   AGE
metrics-server-7566d596c8-fks6z          0/1     CrashLoopBackOff   16         60m
local-path-provisioner-6d59f47c7-ff9bg   0/1     CrashLoopBackOff   17         60m
coredns-7944c66d8d-zgkzs                 0/1     CrashLoopBackOff   17         60m
helm-install-traefik-mg6lk               0/1     CrashLoopBackOff   15         60m

# Killing the pod has no effect since the '*.log' file error will show up again.
[root@fox ~]# ./k3s kubectl delete pod coredns-7944c66d8d-zgkzs -n kube-system
pod "coredns-7944c66d8d-zgkzs" deleted

[root@fox ~]# ./k3s  kubectl logs -n kube-system coredns-7944c66d8d-56wsb
failed to try resolving symlinks in path "/var/log/pods/kube-system_coredns-7944c66d8d-56wsb_3f769173-b718-4cd7-9c04-095025f2276e/coredns/2.log": lstat /var/log/pods/kube-system_coredns-7944c66d8d-56wsb_3f769173-b718-4cd7-9c04-095025f2276e/coredns/2.log: no such file or directory

What do you see if you 'kubectl describe pod -n kube-system coredns - in particular, what sort of events do you have? Do you have any errors in journalctl -u k3s?

Below is the output when describing the coredns pod.
[root@fox ~]# ./k3s kubectl describe pod coredns-7944c66d8d-jggkr -n kube-system
Name:           coredns-7944c66d8d-jggkr
Namespace:      kube-system
Priority:       0
Node:           fox/<IP_ADDRESS>
Start Time:     Tue, 25 Aug 2020 08:23:34 +0200
Labels:         k8s-app=kube-dns
                pod-template-hash=7944c66d8d
Annotations:    <none>
Status:         Running
IP:
IPs:            <none>
Controlled By:  ReplicaSet/coredns-7944c66d8d
Containers:
  coredns:
    Container ID:  containerd://48d1f3f9b3745fb52ec56d36e7ac6c1645caa3dcbc716eadd4ee95b678d7b527
    Image:         rancher/coredns-coredns:1.6.9
    Image ID:      docker.io/rancher/coredns-coredns@sha256:e70c936deab8efed89db66f04847fec137dbb81d5b456e8068b6e71cb770f6c0
    Ports:         53/UDP, 53/TCP, 9153/TCP
    Host Ports:    0/UDP, 0/TCP, 0/TCP
    Args:
      -conf
      /etc/coredns/Corefile
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       StartError
      Message:      sandbox container "65dbdba0f063f788f8b2d582928503a829efc5834200a74e3f3c22e5dff77862" is not running
      Exit Code:    128
      Started:      Thu, 01 Jan 1970 01:00:00 +0100
      Finished:     Tue, 25 Aug 2020 08:24:07 +0200
    Ready:          False
    Restart Count:  3
    Limits:
      memory:  170Mi
    Requests:
      cpu:        100m
      memory:     70Mi
    Liveness:     http-get http://:8080/health delay=60s timeout=5s period=10s #success=1 #failure=5
    Readiness:    http-get http://:8181/ready delay=10s timeout=5s period=10s #success=1 #failure=5
    Environment:  <none>
    Mounts:
      /etc/coredns from config-volume (ro)
      /var/run/secrets/kubernetes.io/serviceaccount from coredns-token-dgg8g (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  config-volume:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      coredns
    Optional:  false
  coredns-token-dgg8g:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  coredns-token-dgg8g
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  beta.kubernetes.io/os=linux
Tolerations:     CriticalAddonsOnly
                 node-role.kubernetes.io/master:NoSchedule
                 node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason          Age                 From               Message
  ----     ------          ----                ----               -------
  Normal   Scheduled       <unknown>           default-scheduler  Successfully assigned kube-system/coredns-7944c66d8d-jggkr to fox
  Warning  Failed          45s                 kubelet, fox       Error: failed to create containerd task: OCI runtime create failed: container_linux.go:341: creating new parent process caused "container_linux.go:1923: running lstat on namespace path \"/proc/28443/ns/ipc\" caused \"lstat /proc/28443/ns/ipc: no such file or directory\"": unknown
  Normal   Pulled          44s (x2 over 45s)   kubelet, fox       Container image "rancher/coredns-coredns:1.6.9" already present on machine
  Normal   Created         44s (x2 over 45s)   kubelet, fox       Created container coredns
  Warning  Failed          44s                 kubelet, fox       Error: sandbox container "503b3a5522dab20234b681026bbb3f6e2142071a01fffc1518a85a6878cf2c04" is not running
  Normal   SandboxChanged  35s (x10 over 44s)  kubelet, fox       Pod sandbox changed, it will be killed and re-created.
  Warning  BackOff         35s (x9 over 43s)   kubelet, fox       Back-off restarting failed container

The logging of the k3s service shows a lot of the following messages:
W0825 08:25:24.800481    1540 watcher.go:87] Error while processing event ("/sys/fs/cgroup/cpu,cpuacct/kubepods/burstable/pod8c727328-93e9-46fe-8184-3add823cf15d/b37f39d65e02a99f29b4f3119ab49d9e06fdf7a46b40afeb7f56a62d8c634073": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/cpu,cpuacct/kubepods/burstable/pod8c727328-93e9-46fe-8184-3add823cf15d/b37f39d65e02a99f29b4f3119ab49d9e06fdf7a46b40afeb7f56a62d8c634073: no such file or directory
W0825 08:25:24.800501    1540 watcher.go:87] Error while processing event ("/sys/fs/cgroup/pids/kubepods/burstable/pod8c727328-93e9-46fe-8184-3add823cf15d/b37f39d65e02a99f29b4f3119ab49d9e06fdf7a46b40afeb7f56a62d8c634073": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/pids/kubepods/burstable/pod8c727328-93e9-46fe-8184-3add823cf15d/b37f39d65e02a99f29b4f3119ab49d9e06fdf7a46b40afeb7f56a62d8c634073: no such file or directory
W0825 08:25:24.800525    1540 watcher.go:87] Error while processing event ("/sys/fs/cgroup/blkio/kubepods/burstable/pod8c727328-93e9-46fe-8184-3add823cf15d/b37f39d65e02a99f29b4f3119ab49d9e06fdf7a46b40afeb7f56a62d8c634073": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/blkio/kubepods/burstable/pod8c727328-93e9-46fe-8184-3add823cf15d/b37f39d65e02a99f29b4f3119ab49d9e06fdf7a46b40afeb7f56a62d8c634073: no such file or directory
W0825 08:25:24.800543    1540 watcher.go:87] Error while processing event ("/sys/fs/cgroup/cpuset/kubepods/besteffort/poddd2fed4d-6c2a-46d4-b164-f7da25ad113d/e503c468d7b6d12d2a75bd85302863eb4dc2dfdfbe7ad3ae13cae4031f2006c0": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/cpuset/kubepods/besteffort/poddd2fed4d-6c2a-46d4-b164-f7da25ad113d/e503c468d7b6d12d2a75bd85302863eb4dc2dfdfbe7ad3ae13cae4031f2006c0: no such file or directory
W0825 08:25:24.800565    1540 watcher.go:87] Error while processing event ("/sys/fs/cgroup/devices/kubepods/besteffort/poddd2fed4d-6c2a-46d4-b164-f7da25ad113d/e503c468d7b6d12d2a75bd85302863eb4dc2dfdfbe7ad3ae13cae4031f2006c0": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/devices/kubepods/besteffort/poddd2fed4d-6c2a-46d4-b164-f7da25ad113d/e503c468d7b6d12d2a75bd85302863eb4dc2dfdfbe7ad3ae13cae4031f2006c0: no such file or directory
W0825 08:25:24.800582    1540 watcher.go:87] Error while processing event ("/sys/fs/cgroup/memory/kubepods/besteffort/poddd2fed4d-6c2a-46d4-b164-f7da25ad113d/e503c468d7b6d12d2a75bd85302863eb4dc2dfdfbe7ad3ae13cae4031f2006c0": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/memory/kubepods/besteffort/poddd2fed4d-6c2a-46d4-b164-f7da25ad113d/e503c468d7b6d12d2a75bd85302863eb4dc2dfdfbe7ad3ae13cae4031f2006c0: no such file or directory
W0825 08:25:24.800603    1540 watcher.go:87] Error while processing event ("/sys/fs/cgroup/cpu,cpuacct/kubepods/besteffort/poddd2fed4d-6c2a-46d4-b164-f7da25ad113d/e503c468d7b6d12d2a75bd85302863eb4dc2dfdfbe7ad3ae13cae4031f2006c0": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/cpu,cpuacct/kubepods/besteffort/poddd2fed4d-6c2a-46d4-b164-f7da25ad113d/e503c468d7b6d12d2a75bd85302863eb4dc2dfdfbe7ad3ae13cae4031f2006c0: no such file or directory
W0825 08:25:24.801650    1540 watcher.go:87] Error while processing event ("/sys/fs/cgroup/pids/kubepods/besteffort/poddd2fed4d-6c2a-46d4-b164-f7da25ad113d/e503c468d7b6d12d2a75bd85302863eb4dc2dfdfbe7ad3ae13cae4031f2006c0": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/pids/kubepods/besteffort/poddd2fed4d-6c2a-46d4-b164-f7da25ad113d/e503c468d7b6d12d2a75bd85302863eb4dc2dfdfbe7ad3ae13cae4031f2006c0: no such file or directory
W0825 08:25:24.801682    1540 watcher.go:87] Error while processing event ("/sys/fs/cgroup/blkio/kubepods/besteffort/poddd2fed4d-6c2a-46d4-b164-f7da25ad113d/e503c468d7b6d12d2a75bd85302863eb4dc2dfdfbe7ad3ae13cae4031f2006c0": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/blkio/kubepods/besteffort/poddd2fed4d-6c2a-46d4-b164-f7da25ad113d/e503c468d7b6d12d2a75bd85302863eb4dc2dfdfbe7ad3ae13cae4031f2006c0: no such file or directory
W0825 08:25:24.801732    1540 watcher.go:87] Error while processing event ("/sys/fs/cgroup/cpuset/kubepods/besteffort/pod24b2bd47-47e0-49c6-9b10-7ce62c75a662/b71b5d2378a3a0ae21c2b5caae2109ef7d1d88a7ea53cc841dd92cc10e32da83": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/cpuset/kubepods/besteffort/pod24b2bd47-47e0-49c6-9b10-7ce62c75a662/b71b5d2378a3a0ae21c2b5caae2109ef7d1d88a7ea53cc841dd92cc10e32da83: no such file or directory
W0825 08:25:24.801754    1540 watcher.go:87] Error while processing event ("/sys/fs/cgroup/devices/kubepods/besteffort/pod24b2bd47-47e0-49c6-9b10-7ce62c75a662/b71b5d2378a3a0ae21c2b5caae2109ef7d1d88a7ea53cc841dd92cc10e32da83": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/devices/kubepods/besteffort/pod24b2bd47-47e0-49c6-9b10-7ce62c75a662/b71b5d2378a3a0ae21c2b5caae2109ef7d1d88a7ea53cc841dd92cc10e32da83: no such file or directory
W0825 08:25:24.801771    1540 watcher.go:87] Error while processing event ("/sys/fs/cgroup/memory/kubepods/besteffort/pod24b2bd47-47e0-49c6-9b10-7ce62c75a662/b71b5d2378a3a0ae21c2b5caae2109ef7d1d88a7ea53cc841dd92cc10e32da83": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/memory/kubepods/besteffort/pod24b2bd47-47e0-49c6-9b10-7ce62c75a662/b71b5d2378a3a0ae21c2b5caae2109ef7d1d88a7ea53cc841dd92cc10e32da83: no such file or directory
W0825 08:25:24.801791    1540 watcher.go:87] Error while processing event ("/sys/fs/cgroup/cpu,cpuacct/kubepods/besteffort/pod24b2bd47-47e0-49c6-9b10-7ce62c75a662/b71b5d2378a3a0ae21c2b5caae2109ef7d1d88a7ea53cc841dd92cc10e32da83": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/cpu,cpuacct/kubepods/besteffort/pod24b2bd47-47e0-49c6-9b10-7ce62c75a662/b71b5d2378a3a0ae21c2b5caae2109ef7d1d88a7ea53cc841dd92cc10e32da83: no such file or directory
W0825 08:25:24.801904    1540 watcher.go:87] Error while processing event ("/sys/fs/cgroup/pids/kubepods/besteffort/pod24b2bd47-47e0-49c6-9b10-7ce62c75a662/b71b5d2378a3a0ae21c2b5caae2109ef7d1d88a7ea53cc841dd92cc10e32da83": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/pids/kubepods/besteffort/pod24b2bd47-47e0-49c6-9b10-7ce62c75a662/b71b5d2378a3a0ae21c2b5caae2109ef7d1d88a7ea53cc841dd92cc10e32da83: no such file or directory
W0825 08:25:24.801932    1540 watcher.go:87] Error while processing event ("/sys/fs/cgroup/blkio/kubepods/besteffort/pod24b2bd47-47e0-49c6-9b10-7ce62c75a662/b71b5d2378a3a0ae21c2b5caae2109ef7d1d88a7ea53cc841dd92cc10e32da83": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/blkio/kubepods/besteffort/pod24b2bd47-47e0-49c6-9b10-7ce62c75a662/b71b5d2378a3a0ae21c2b5caae2109ef7d1d88a7ea53cc841dd92cc10e32da83: no such file or directory
W0825 08:25:25.698406    1540 pod_container_deletor.go:77] Container "b71b5d2378a3a0ae21c2b5caae2109ef7d1d88a7ea53cc841dd92cc10e32da83" not found in pod's containers
E0825 08:25:25.987789    1540 pod_workers.go:191] Error syncing pod 1ab9db4b-5a1e-42ce-ac82-86d9480963a2 ("metrics-server-7566d596c8-fks6z_kube-system(1ab9db4b-5a1e-42ce-ac82-86d9480963a2)"), skipping: failed to "StartContainer" for "metrics-server" with CrashLoopBackOff: "back-off 5m0s restarting failed container=metrics-server pod=metrics-server-7566d596c8-fks6z_kube-system(1ab9db4b-5a1e-42ce-ac82-86d9480963a2)"
E0825 08:25:26.266633    1540 pod_workers.go:191] Error syncing pod 8c727328-93e9-46fe-8184-3add823cf15d ("coredns-7944c66d8d-jggkr_kube-system(8c727328-93e9-46fe-8184-3add823cf15d)"), skipping: failed to "StartContainer" for "coredns" with CrashLoopBackOff: "back-off 1m20s restarting failed container=coredns pod=coredns-7944c66d8d-jggkr_kube-system(8c727328-93e9-46fe-8184-3add823cf15d)"
E0825 08:25:26.270030    1540 pod_workers.go:191] Error syncing pod dd2fed4d-6c2a-46d4-b164-f7da25ad113d ("helm-install-traefik-mg6lk_kube-system(dd2fed4d-6c2a-46d4-b164-f7da25ad113d)"), skipping: failed to "StartContainer" for "helm" with CrashLoopBackOff: "back-off 5m0s restarting failed container=helm pod=helm-install-traefik-mg6lk_kube-system(dd2fed4d-6c2a-46d4-b164-f7da25ad113d)"
W0825 08:25:26.371296    1540 manager.go:1131] Failed to process watch event {EventType:0 Name:/kubepods/besteffort/pod1ab9db4b-5a1e-42ce-ac82-86d9480963a2/4344d35c33bdbd5bc303057ce177cfe754493f9cdc2162f31ea19da8d05f3fe7 WatchSource:0}: task 4344d35c33bdbd5bc303057ce177cfe754493f9cdc2162f31ea19da8d05f3fe7 not found: not found
W0825 08:25:26.371354    1540 watcher.go:87] Error while processing event ("/sys/fs/cgroup/devices/kubepods/besteffort/pod1ab9db4b-5a1e-42ce-ac82-86d9480963a2/4ff98e73bbb8cb3c6c6de4331cc89b2d3f847d767a688810503aeca38e03fb76": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/devices/kubepods/besteffort/pod1ab9db4b-5a1e-42ce-ac82-86d9480963a2/4ff98e73bbb8cb3c6c6de4331cc89b2d3f847d767a688810503aeca38e03fb76: no such file or directory
W0825 08:25:26.371388    1540 watcher.go:87] Error while processing event ("/sys/fs/cgroup/memory/kubepods/besteffort/pod1ab9db4b-5a1e-42ce-ac82-86d9480963a2/4ff98e73bbb8cb3c6c6de4331cc89b2d3f847d767a688810503aeca38e03fb76": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/memory/kubepods/besteffort/pod1ab9db4b-5a1e-42ce-ac82-86d9480963a2/4ff98e73bbb8cb3c6c6de4331cc89b2d3f847d767a688810503aeca38e03fb76: no such file or directory
W0825 08:25:26.371407    1540 watcher.go:87] Error while processing event ("/sys/fs/cgroup/cpu,cpuacct/kubepods/besteffort/pod1ab9db4b-5a1e-42ce-ac82-86d9480963a2/4ff98e73bbb8cb3c6c6de4331cc89b2d3f847d767a688810503aeca38e03fb76": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/cpu,cpuacct/kubepods/besteffort/pod1ab9db4b-5a1e-42ce-ac82-86d9480963a2/4ff98e73bbb8cb3c6c6de4331cc89b2d3f847d767a688810503aeca38e03fb76: no such file or directory
W0825 08:25:26.371429    1540 watcher.go:87] Error while processing event ("/sys/fs/cgroup/pids/kubepods/besteffort/pod1ab9db4b-5a1e-42ce-ac82-86d9480963a2/4ff98e73bbb8cb3c6c6de4331cc89b2d3f847d767a688810503aeca38e03fb76": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/pids/kubepods/besteffort/pod1ab9db4b-5a1e-42ce-ac82-86d9480963a2/4ff98e73bbb8cb3c6c6de4331cc89b2d3f847d767a688810503aeca38e03fb76: no such file or directory
W0825 08:25:26.371453    1540 watcher.go:87] Error while processing event ("/sys/fs/cgroup/blkio/kubepods/besteffort/pod1ab9db4b-5a1e-42ce-ac82-86d9480963a2/4ff98e73bbb8cb3c6c6de4331cc89b2d3f847d767a688810503aeca38e03fb76": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/blkio/kubepods/besteffort/pod1ab9db4b-5a1e-42ce-ac82-86d9480963a2/4ff98e73bbb8cb3c6c6de4331cc89b2d3f847d767a688810503aeca38e03fb76: no such file or directory
W0825 08:25:26.371548    1540 watcher.go:87] Error while processing event ("/sys/fs/cgroup/cpuset/kubepods/burstable/pod8c727328-93e9-46fe-8184-3add823cf15d/99d2bbf0ae53616aaa28c411161bc2a402cc2645c1218a2e03eac4a6b58594a0": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/cpuset/kubepods/burstable/pod8c727328-93e9-46fe-8184-3add823cf15d/99d2bbf0ae53616aaa28c411161bc2a402cc2645c1218a2e03eac4a6b58594a0: no such file or directory
W0825 08:25:26.371571    1540 watcher.go:87] Error while processing event ("/sys/fs/cgroup/devices/kubepods/burstable/pod8c727328-93e9-46fe-8184-3add823cf15d/99d2bbf0ae53616aaa28c411161bc2a402cc2645c1218a2e03eac4a6b58594a0": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/devices/kubepods/burstable/pod8c727328-93e9-46fe-8184-3add823cf15d/99d2bbf0ae53616aaa28c411161bc2a402cc2645c1218a2e03eac4a6b58594a0: no such file or directory
W0825 08:25:26.371588    1540 watcher.go:87] Error while processing event ("/sys/fs/cgroup/memory/kubepods/burstable/pod8c727328-93e9-46fe-8184-3add823cf15d/99d2bbf0ae53616aaa28c411161bc2a402cc2645c1218a2e03eac4a6b58594a0": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/memory/kubepods/burstable/pod8c727328-93e9-46fe-8184-3add823cf15d/99d2bbf0ae53616aaa28c411161bc2a402cc2645c1218a2e03eac4a6b58594a0: no such file or directory
W0825 08:25:26.371608    1540 watcher.go:87] Error while processing event ("/sys/fs/cgroup/cpu,cpuacct/kubepods/burstable/pod8c727328-93e9-46fe-8184-3add823cf15d/99d2bbf0ae53616aaa28c411161bc2a402cc2645c1218a2e03eac4a6b58594a0": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/cpu,cpuacct/kubepods/burstable/pod8c727328-93e9-46fe-8184-3add823cf15d/99d2bbf0ae53616aaa28c411161bc2a402cc2645c1218a2e03eac4a6b58594a0: no such file or directory
W0825 08:25:26.371625    1540 watcher.go:87] Error while processing event ("/sys/fs/cgroup/pids/kubepods/burstable/pod8c727328-93e9-46fe-8184-3add823cf15d/99d2bbf0ae53616aaa28c411161bc2a402cc2645c1218a2e03eac4a6b58594a0": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/pids/kubepods/burstable/pod8c727328-93e9-46fe-8184-3add823cf15d/99d2bbf0ae53616aaa28c411161bc2a402cc2645c1218a2e03eac4a6b58594a0: no such file or directory
W0825 08:25:26.371646    1540 watcher.go:87] Error while processing event ("/sys/fs/cgroup/blkio/kubepods/burstable/pod8c727328-93e9-46fe-8184-3add823cf15d/99d2bbf0ae53616aaa28c411161bc2a402cc2645c1218a2e03eac4a6b58594a0": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/blkio/kubepods/burstable/pod8c727328-93e9-46fe-8184-3add823cf15d/99d2bbf0ae53616aaa28c411161bc2a402cc2645c1218a2e03eac4a6b58594a0: no such file or directory
W0825 08:25:26.371663    1540 watcher.go:87] Error while processing event ("/sys/fs/cgroup/cpuset/kubepods/besteffort/poddd2fed4d-6c2a-46d4-b164-f7da25ad113d/b24c079faed0c1b2b1d2b0d2ee6a982cc80edb32a803135a7a1d0e72fc7f0469": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/cpuset/kubepods/besteffort/poddd2fed4d-6c2a-46d4-b164-f7da25ad113d/b24c079faed0c1b2b1d2b0d2ee6a982cc80edb32a803135a7a1d0e72fc7f0469: no such file or directory
W0825 08:25:26.371684    1540 watcher.go:87] Error while processing event ("/sys/fs/cgroup/devices/kubepods/besteffort/poddd2fed4d-6c2a-46d4-b164-f7da25ad113d/b24c079faed0c1b2b1d2b0d2ee6a982cc80edb32a803135a7a1d0e72fc7f0469": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/devices/kubepods/besteffort/poddd2fed4d-6c2a-46d4-b164-f7da25ad113d/b24c079faed0c1b2b1d2b0d2ee6a982cc80edb32a803135a7a1d0e72fc7f0469: no such file or directory
W0825 08:25:26.371700    1540 watcher.go:87] Error while processing event ("/sys/fs/cgroup/memory/kubepods/besteffort/poddd2fed4d-6c2a-46d4-b164-f7da25ad113d/b24c079faed0c1b2b1d2b0d2ee6a982cc80edb32a803135a7a1d0e72fc7f0469": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/memory/kubepods/besteffort/poddd2fed4d-6c2a-46d4-b164-f7da25ad113d/b24c079faed0c1b2b1d2b0d2ee6a982cc80edb32a803135a7a1d0e72fc7f0469: no such file or directory
W0825 08:25:26.372148    1540 watcher.go:87] Error while processing event ("/sys/fs/cgroup/cpu,cpuacct/kubepods/besteffort/poddd2fed4d-6c2a-46d4-b164-f7da25ad113d/b24c079faed0c1b2b1d2b0d2ee6a982cc80edb32a803135a7a1d0e72fc7f0469": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/cpu,cpuacct/kubepods/besteffort/poddd2fed4d-6c2a-46d4-b164-f7da25ad113d/b24c079faed0c1b2b1d2b0d2ee6a982cc80edb32a803135a7a1d0e72fc7f0469: no such file or directory
W0825 08:25:26.372171    1540 watcher.go:87] Error while processing event ("/sys/fs/cgroup/pids/kubepods/besteffort/poddd2fed4d-6c2a-46d4-b164-f7da25ad113d/b24c079faed0c1b2b1d2b0d2ee6a982cc80edb32a803135a7a1d0e72fc7f0469": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/pids/kubepods/besteffort/poddd2fed4d-6c2a-46d4-b164-f7da25ad113d/b24c079faed0c1b2b1d2b0d2ee6a982cc80edb32a803135a7a1d0e72fc7f0469: no such file or directory
W0825 08:25:26.372192    1540 watcher.go:87] Error while processing event ("/sys/fs/cgroup/blkio/kubepods/besteffort/poddd2fed4d-6c2a-46d4-b164-f7da25ad113d/b24c079faed0c1b2b1d2b0d2ee6a982cc80edb32a803135a7a1d0e72fc7f0469": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/blkio/kubepods/besteffort/poddd2fed4d-6c2a-46d4-b164-f7da25ad113d/b24c079faed0c1b2b1d2b0d2ee6a982cc80edb32a803135a7a1d0e72fc7f0469: no such file or directory
E0825 08:25:26.703457    1540 pod_workers.go:191] Error syncing pod 24b2bd47-47e0-49c6-9b10-7ce62c75a662 ("local-path-provisioner-6d59f47c7-ff9bg_kube-system(24b2bd47-47e0-49c6-9b10-7ce62c75a662)"), skipping: failed to "StartContainer" for "local-path-provisioner" with CrashLoopBackOff: "back-off 5m0s restarting failed container=local-path-provisioner pod=local-path-provisioner-6d59f47c7-ff9bg_kube-system(24b2bd47-47e0-49c6-9b10-7ce62c75a662)"
W0825 08:25:26.709169    1540 pod_container_deletor.go:77] Container "99d2bbf0ae53616aaa28c411161bc2a402cc2645c1218a2e03eac4a6b58594a0" not found in pod's containers
W0825 08:25:26.733912    1540 pod_container_deletor.go:77] Container "b24c079faed0c1b2b1d2b0d2ee6a982cc80edb32a803135a7a1d0e72fc7f0469" not found in pod's containers
W0825 08:25:26.747738    1540 pod_container_deletor.go:77] Container "4ff98e73bbb8cb3c6c6de4331cc89b2d3f847d767a688810503aeca38e03fb76" not found in pod's containers
W0825 08:25:27.765191    1540 pod_container_deletor.go:77] Container "d618da3d4d1a09d243ccd4f19f948702c8265c46970ce6a2905fadb8da428a43" not found in pod's containers

All other pods have the same type of event:
  Warning  Failed          19s                kubelet, fox       Error: failed to create containerd task: OCI runtime create failed: container_linux.go:341: creating new parent process caused "container_linux.go:1923: running lstat on namespace path \"/proc/23578/ns/ipc\" caused \"lstat /proc/23578/ns/ipc: no such file or directory\"": unknown

It seems that containerd is not able to create the container?

@vvanouytsel given your installation method I suspect that you do not have the k3s-selinux policy installed. This is something that you would be guided to if you attempt to install via the install.sh:
# on a clean centos/7 vagrant box
[vagrant@localhost ~]$ curl -sfL https://get.k3s.io | sh -
[INFO]  Finding release for channel stable
[INFO]  Using v1.18.8+k3s1 as release
[INFO]  Downloading hash https://github.com/rancher/k3s/releases/download/v1.18.8+k3s1/sha256sum-amd64.txt
[INFO]  Downloading binary https://github.com/rancher/k3s/releases/download/v1.18.8+k3s1/k3s
[INFO]  Verifying binary download
[INFO]  Installing k3s to /usr/local/bin/k3s
[ERROR]  Failed to find the k3s-selinux policy, please install:
    yum install -y container-selinux selinux-policy-base
    rpm -i https://rpm.rancher.io/k3s-selinux-0.1.1-rc1.el7.noarch.rpm

I've manually installed the following packages.
$ sudo yum -y install container-selinux selinux-policy-base https://rpm.rancher.io/k3s-selinux-0.1.1-rc1.el7.noarch.rpm

I've deleted the coredns pod and it still throws the following error:
failed to create containerd task: OCI runtime create failed: container_linux.go:341: creating new parent process caused "container_linux.go:1923: running lstat on namespace path \"/proc/3230/ns/ipc\" caused \"lstat /proc/3230/ns/ipc: no such file or directory\"": unknown
[root@fox ~]# ./k3s kubectl describe pod coredns-7944c66d8d-hbcz5 -n kube-system
Name:         coredns-7944c66d8d-hbcz5
Namespace:    kube-system
Priority:     0
Node:         fox/<IP_ADDRESS>
Start Time:   Wed, 26 Aug 2020 08:54:58 +0200
Labels:       k8s-app=kube-dns
              pod-template-hash=7944c66d8d
Annotations:  <none>
Status:       Running
IP:           <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/coredns-7944c66d8d
Containers:
  coredns:
    Container ID:  containerd://fdf7fc0c6d540d280cd2f7181263f0e61859324eaf7941f8036db8b44660ce9a
    Image:         rancher/coredns-coredns:1.6.9
    Image ID:      docker.io/rancher/coredns-coredns@sha256:e70c936deab8efed89db66f04847fec137dbb81d5b456e8068b6e71cb770f6c0
    Ports:         53/UDP, 53/TCP, 9153/TCP
    Host Ports:    0/UDP, 0/TCP, 0/TCP
    Args:
      -conf
      /etc/coredns/Corefile
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       StartError
      Message:      failed to create containerd task: OCI runtime create failed: container_linux.go:341: creating new parent process caused "container_linux.go:1923: running lstat on namespace path \"/proc/3230/ns/ipc\" caused \"lstat /proc/3230/ns/ipc: no such file or directory\"": unknown
      Exit Code:    128
      Started:      Thu, 01 Jan 1970 01:00:00 +0100
      Finished:     Wed, 26 Aug 2020 09:00:14 +0200
    Ready:          False
    Restart Count:  6
    Limits:
      memory:  170Mi
    Requests:
      cpu:        100m
      memory:     70Mi
    Liveness:     http-get http://:8080/health delay=60s timeout=5s period=10s #success=1 #failure=5
    Readiness:    http-get http://:8181/ready delay=10s timeout=5s period=10s #success=1 #failure=5
    Environment:  <none>
    Mounts:
      /etc/coredns from config-volume (ro)
      /var/run/secrets/kubernetes.io/serviceaccount from coredns-token-dgg8g (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  config-volume:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      coredns
    Optional:  false
  coredns-token-dgg8g:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  coredns-token-dgg8g
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  beta.kubernetes.io/os=linux
Tolerations:     CriticalAddonsOnly
                 node-role.kubernetes.io/master:NoSchedule
                 node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason          Age                      From               Message
  ----     ------          ----                     ----               -------
  Normal   Scheduled       <unknown>                default-scheduler  Successfully assigned kube-system/coredns-7944c66d8d-hbcz5 to fox
  Warning  Failed          8m46s                    kubelet, fox       Error: sandbox container "2ec9443b4e298c39baf9a87886ff49a537604f24af1735533c018bc93ded464e" is not running
  Normal   Pulled          8m45s (x2 over 8m46s)    kubelet, fox       Container image "rancher/coredns-coredns:1.6.9" already present on machine
  Normal   Created         8m45s (x2 over 8m46s)    kubelet, fox       Created container coredns
  Warning  Failed          8m45s                    kubelet, fox       Error: sandbox container "d079b26b00982c83cd455df99be3158c67eb93d9af6de67730fb95015abe03fd" is not running
  Normal   SandboxChanged  8m36s (x10 over 8m45s)   kubelet, fox       Pod sandbox changed, it will be killed and re-created.
  Warning  BackOff         3m46s (x142 over 8m44s)  kubelet, fox       Back-off restarting failed container

I've also tried the k3s install script on a clean CentOS 7.8 vagrant box, and that worked perfectly.
So I guess my next steps are to look through the k3s install script and verify what else it is doing.
For my use case I would like to simply drop the k3s binary using Ansible, instead of running the install script.

After some more testing I can confirm that everything works fine as long as I install the selinux packages before running k3s server.
$ sudo yum -y install container-selinux selinux-policy-base https://rpm.rancher.io/k3s-selinux-0.1.1-rc1.el7.noarch.rpm

On the broken system where I installed the selinux packages after I already started k3s, I had to do the following:

Manually delete all pods/deployments/statefulsets/jobs/

[root@localhost ~]# k3s kubectl delete deploy,job,statefulset,pod --all-namespaces --all

Restart k3s
Recreate all deployments/statefulsets/jobs/...

Containerd is now able to successfully start the containers.
[root@localhost ~]# k3s kubectl get pods -n kube-system
NAME                                     READY   STATUS      RESTARTS   AGE
local-path-provisioner-6d59f47c7-bgh8w   1/1     Running     0          3m8s
metrics-server-7566d596c8-msdcb          1/1     Running     0          3m8s
coredns-7944c66d8d-t2j8d                 1/1     Running     0          3m8s
helm-install-traefik-r8nqs               0/1     Completed   2          3m9s
svclb-traefik-qf59d                      2/2     Running     0          2m49s
traefik-758cd5fc85-fcttx                 1/1     Running     0          2m49s

If you'd installed from the script, it would have checked for this on install to ensure that you got the package in before starting k3s for the first time. It would have also dropped a k3s-killall.sh that you could have used to terminate the pods so that they could be recreated with the correct context. Although in this case, I suspect that just restarting the node (which would have recreated the pods) would have fixed your issue as well.

@vvanouytsel it looks like your issue has been solved then per above? If so, I will close this out.
FWIW, I recreated the problem you had and came to the same resolution as the workaround.
As @brandond mentioned, the simpler install steps would just be to install k3s from the script:
$ sudo yum -y install container-selinux selinux-policy-base https://rpm.rancher.io/k3s-selinux-0.1.1-rc1.el7.noarch.rpm
...
$ curl -sfL https://get.k3s.io | INSTALL_K3S_VERSION=v1.18.8+k3s1 sh -

If you run the install script before installing selinux policy, you'll get an error like:
[ERROR]  Failed to find the k3s-selinux policy, please install:
    yum install -y container-selinux selinux-policy-base
    rpm -i https://rpm.rancher.io/k3s-selinux-0.1.1-rc1.el7.noarch.rpm

@brandond restarting the node does not solve the issue.
Restarting the pods also does not solve the issue.
Previously I thought that removing the parent resources (Deployments, Statefulsets, Jobs, Daemonsets, ...) and recreating them would fix the issue after the SElinux packages are installed, but this does not seem the case.
[root@localhost ~]# yum list installed | grep selinux
container-selinux.noarch           2:2.119.2-1.911c772.el7_8  @extras
k3s-selinux.noarch                 0.1.1-rc1.el7              @/k3s-selinux-0.1.1-rc1.el7.noarch
libselinux.x86_64                  2.5-15.el7                 @anaconda
libselinux-python.x86_64           2.5-15.el7                 @anaconda
libselinux-utils.x86_64            2.5-15.el7                 @anaconda
selinux-policy.noarch              3.13.1-266.el7_8.1         @updates
selinux-policy-targeted.noarch     3.13.1-266.el7_8.1         @updates

After restarting k3s, the pods still stay in CrashLoopBackOff.
Even a reboot did not solve the issue.
[root@localhost ~]# k3s kubectl describe pod  coredns-7944c66d8d-kz6c9  -n kube-system
Name:         coredns-7944c66d8d-kz6c9
Namespace:    kube-system
Priority:     0
Node:         localhost.localdomain/<IP_ADDRESS>
Start Time:   Thu, 27 Aug 2020 07:35:01 +0000
Labels:       k8s-app=kube-dns
              pod-template-hash=7944c66d8d
Annotations:  <none>
Status:       Running
IP:           <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/coredns-7944c66d8d
Containers:
  coredns:
    Container ID:  containerd://ca691db5d74e63e2991532b3b0fedf681ae638f55f5c6335435f34e937601e03
    Image:         rancher/coredns-coredns:1.6.9
    Image ID:      docker.io/rancher/coredns-coredns@sha256:e70c936deab8efed89db66f04847fec137dbb81d5b456e8068b6e71cb770f6c0
    Ports:         53/UDP, 53/TCP, 9153/TCP
    Host Ports:    0/UDP, 0/TCP, 0/TCP
    Args:
      -conf
      /etc/coredns/Corefile
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       StartError
      Message:      failed to create containerd task: OCI runtime create failed: container_linux.go:341: creating new parent process caused "container_linux.go:1923: running lstat on namespace path \"/proc/8575/ns/ipc\" caused \"lstat /proc/8575/ns/ipc: no such file or directory\"": unknown
      Exit Code:    128
      Started:      Thu, 01 Jan 1970 00:00:00 +0000
      Finished:     Thu, 27 Aug 2020 07:36:14 +0000
    Ready:          False
    Restart Count:  3
    Limits:
      memory:  170Mi
    Requests:
      cpu:        100m
      memory:     70Mi
    Liveness:     http-get http://:8080/health delay=60s timeout=5s period=10s #success=1 #failure=5
    Readiness:    http-get http://:8181/ready delay=10s timeout=5s period=10s #success=1 #failure=5
    Environment:  <none>
    Mounts:
      /etc/coredns from config-volume (ro)
      /var/run/secrets/kubernetes.io/serviceaccount from coredns-token-shz7k (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  config-volume:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      coredns
    Optional:  false
  coredns-token-shz7k:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  coredns-token-shz7k
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  beta.kubernetes.io/os=linux
Tolerations:     CriticalAddonsOnly
                 node-role.kubernetes.io/master:NoSchedule
                 node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason          Age                 From                            Message
  ----     ------          ----                ----                            -------
  Normal   Scheduled       <unknown>           default-scheduler               Successfully assigned kube-system/coredns-7944c66d8d-kz6c9 to localhost.localdomain
  Normal   Created         92s                 kubelet, localhost.localdomain  Created container coredns
  Warning  Failed          92s                 kubelet, localhost.localdomain  Error: failed to create containerd task: OCI runtime create failed: container_linux.go:341: creating new parent process caused "container_linux.go:1923: running lstat on namespace path \"/proc/1319/ns/ipc\" caused \"lstat /proc/1319/ns/ipc: no such file or directory\"": unknown
  Warning  Failed          92s                 kubelet, localhost.localdomain  Error: failed to get sandbox container task: no running task found: task e93898e9793b58185a060cb356958a5c2d25e8073a385c523e98c0c9360ac2e5 not found: not found
  Warning  BackOff         82s (x9 over 90s)   kubelet, localhost.localdomain  Back-off restarting failed container
  Normal   SandboxChanged  82s (x10 over 91s)  kubelet, localhost.localdomain  Pod sandbox changed, it will be killed and re-created.
  Normal   Pulled          81s (x3 over 92s)   kubelet, localhost.localdomain  Container image "rancher/coredns-coredns:1.6.9" already present on machine

The logs of the k3s server process show the following
W0827 07:37:41.541807    1041 pod_container_deletor.go:77] Container "6443cd5f38821e3b2ceaba1423d5d25c9cf21fb1ba6e12a05102b3e47b6a208e" not found in pod's containers
E0827 07:37:42.291292    1041 pod_workers.go:191] Error syncing pod 758b7454-dfb6-40a5-b228-b9e1a90a7e46 ("coredns-7944c66d8d-kz6c9_kube-system(758b7454-dfb6-40a5-b228-b9e1a90a7e46)"), skipping: failed to "StartContainer" for "coredns" with CrashLoopBackOff: "back-off 2m40s restarting failed container=coredns pod=coredns-7944c66d8d-kz6c9_kube-system(758b7454-dfb6-40a5-b228-b9e1a90a7e46)"
W0827 07:37:42.565331    1041 pod_container_deletor.go:77] Container "bf55cb41babadbbd05bca069a56e6257251d5296e23e8631b332466b9b509c58" not found in pod's containers
W0827 07:37:42.990273    1041 manager.go:1131] Failed to process watch event {EventType:0 Name:/kubepods/burstable/pod758b7454-dfb6-40a5-b228-b9e1a90a7e46/b8141a779ac848b2f1d290cb208f4e5e6025ef7e9cfc119d1ade991284347a4d WatchSource:0}: task b8141a779ac848b2f1d290cb208f4e5e6025ef7e9cfc119d1ade991284347a4d not found: not found
E0827 07:37:43.305835    1041 pod_workers.go:191] Error syncing pod 758b7454-dfb6-40a5-b228-b9e1a90a7e46 ("coredns-7944c66d8d-kz6c9_kube-system(758b7454-dfb6-40a5-b228-b9e1a90a7e46)"), skipping: failed to "StartContainer" for "coredns" with CrashLoopBackOff: "back-off 2m40s restarting failed container=coredns pod=coredns-7944c66d8d-kz6c9_kube-system(758b7454-dfb6-40a5-b228-b9e1a90a7e46)"
W0827 07:37:43.601735    1041 pod_container_deletor.go:77] Container "5f359ff4a23086ad3b1b47543571d6397e8f2a94f9468e4e1e87035cc158455d" not found in pod's containers
E0827 07:37:44.318715    1041 pod_workers.go:191] Error syncing pod 758b7454-dfb6-40a5-b228-b9e1a90a7e46 ("coredns-7944c66d8d-kz6c9_kube-system(758b7454-dfb6-40a5-b228-b9e1a90a7e46)"), skipping: failed to "StartContainer" for "coredns" with CrashLoopBackOff: "back-off 2m40s restarting failed container=coredns pod=coredns-7944c66d8d-kz6c9_kube-system(758b7454-dfb6-40a5-b228-b9e1a90a7e46)"
W0827 07:37:44.494354    1041 manager.go:1131] Failed to process watch event {EventType:0 Name:/kubepods/burstable/pod758b7454-dfb6-40a5-b228-b9e1a90a7e46/6443cd5f38821e3b2ceaba1423d5d25c9cf21fb1ba6e12a05102b3e47b6a208e WatchSource:0}: task 6443cd5f38821e3b2ceaba1423d5d25c9cf21fb1ba6e12a05102b3e47b6a208e not found: not found
W0827 07:37:44.644697    1041 pod_container_deletor.go:77] Container "6381906248ec765455a9b723f03d972a170344c425110a62a39c8467fd6d4804" not found in pod's containers
E0827 07:37:45.398486    1041 pod_workers.go:191] Error syncing pod 758b7454-dfb6-40a5-b228-b9e1a90a7e46 ("coredns-7944c66d8d-kz6c9_kube-system(758b7454-dfb6-40a5-b228-b9e1a90a7e46)"), skipping: failed to "StartContainer" for "coredns" with CrashLoopBackOff: "back-off 2m40s restarting failed container=coredns pod=coredns-7944c66d8d-kz6c9_kube-system(758b7454-dfb6-40a5-b228-b9e1a90a7e46)"
W0827 07:37:45.668889    1041 pod_container_deletor.go:77] Container "0e8d7207b07c82f2e39d41f45fbf9b363db20af14c4c7b82fd3f251e851855a6" not found in pod's containers
W0827 07:37:46.002715    1041 manager.go:1131] Failed to process watch event {EventType:0 Name:/kubepods/burstable/pod758b7454-dfb6-40a5-b228-b9e1a90a7e46/bf55cb41babadbbd05bca069a56e6257251d5296e23e8631b332466b9b509c58 WatchSource:0}: task bf55cb41babadbbd05bca069a56e6257251d5296e23e8631b332466b9b509c58 not found: not found
E0827 07:37:46.481327    1041 pod_workers.go:191] Error syncing pod 758b7454-dfb6-40a5-b228-b9e1a90a7e46 ("coredns-7944c66d8d-kz6c9_kube-system(758b7454-dfb6-40a5-b228-b9e1a90a7e46)"), skipping: failed to "StartContainer" for "coredns" with CrashLoopBackOff: "back-off 2m40s restarting failed container=coredns pod=coredns-7944c66d8d-kz6c9_kube-system(758b7454-dfb6-40a5-b228-b9e1a90a7e46)"
W0827 07:37:46.710841    1041 pod_container_deletor.go:77] Container "2e32f3f59af7cbd8412481804aac423b4f4f89b6f35c9a08b9bfdc1ddfaec8a7" not found in pod's containers
E0827 07:37:47.492781    1041 pod_workers.go:191] Error syncing pod 758b7454-dfb6-40a5-b228-b9e1a90a7e46 ("coredns-7944c66d8d-kz6c9_kube-system(758b7454-dfb6-40a5-b228-b9e1a90a7e46)"), skipping: failed to "StartContainer" for "coredns" with CrashLoopBackOff: "back-off 2m40s restarting failed container=coredns pod=coredns-7944c66d8d-kz6c9_kube-system(758b7454-dfb6-40a5-b228-b9e1a90a7e46)"
W0827 07:37:47.505856    1041 manager.go:1131] Failed to process watch event {EventType:0 Name:/kubepods/burstable/pod758b7454-dfb6-40a5-b228-b9e1a90a7e46/5f359ff4a23086ad3b1b47543571d6397e8f2a94f9468e4e1e87035cc158455d WatchSource:0}: task 5f359ff4a23086ad3b1b47543571d6397e8f2a94f9468e4e1e87035cc158455d not found: not found

After installing the SELinux packages I ran restorecon.
restorecon -Rv /

When restarting k3s I found the following SELinux denials in the audit.log file.
[root@localhost ~]# tail -f /var/log/audit/audit.log  | grep avc
type=AVC msg=audit(1598521558.566:303468): avc:  denied  { nnp_transition } for  pid=7707 comm="runc:[2:INIT]" scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tcontext=system_u:system_r:container_t:s0:c123,c672 tclass=process2 permissive=0
type=AVC msg=audit(1598521558.566:303469): avc:  denied  { create } for  pid=7707 comm="runc:[2:INIT]" scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tcontext=system_u:object_r:unlabeled_t:s0 tclass=key permissive=0

So it seems to be something related to runc?

I did some more testing and found the following:
# A working system
[root@localhost ~]# ps -efZ | grep k3s | grep -v grep
unconfined_u:system_r:container_runtime_t:s0-s0:c0.c1023 root 3886 3848  6 09:02 pts/0 00:05:44 k3s server --no-deploy=metrics-server,traefik,servicelb,local-storage
unconfined_u:system_r:container_runtime_t:s0-s0:c0.c1023 root 3906 3886  0 09:02 pts/0 00:00:21 containerd -c /var/lib/rancher/k3s/agent/etc/containerd/config.toml -a /run/k3s/containerd/containerd.sock --state /run/k3s/containerd --root /var/lib/rancher/k3s/agent/containerd
unconfined_u:system_r:container_runtime_t:s0-s0:c0.c1023 root 4126 1  0 09:03 pts/0 00:00:01 /var/lib/rancher/k3s/data/19bb6a9b46ad0013de084cf1e0feb7927ff9e4e06624685ff87f003c208fded1/bin/containerd-shim-runc-v2 -namespace k8s.io -id ce00a7067635cfc1b4bf8eceb3f00c199dc44eb725d91b08194d773f1a816f6e -address /run/k3s/containerd/containerd.sock

# A broken system
[root@localhost ~]# ps -efZ | grep k3s | grep -v grep
unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 root 4420 3057  9 09:45 pts/0 00:04:43 k3s server --no-deploy=metrics-server,traefik,servicelb,local-storage
unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 root 4434 4420  6 09:45 pts/0 00:03:17 containerd -c /var/lib/rancher/k3s/agent/etc/containerd/config.toml -a /run/k3s/containerd/containerd.sock --state /run/k3s/containerd --root /var/lib/rancher/k3s/agent/containerd

Notice that on a working system the container_runtime_t type is used and on the broken system the unconfined_t type is used for the k3s process..

When further investigating the broken system I can see that containerd tries to start a container with image sha256:da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e, which fails so it retries.
# This list gets bigger and bigger
[root@localhost ~]# k3s ctr container list
CONTAINER                                                           IMAGE                                                                      RUNTIME
04ae86f757f2996c0fd682fbd6c7d0da3007e8237d18c2107a011348fba1b5be    sha256:da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e    io.containerd.runc.v2
053ea4e6f01270887437a9f121cecd878f3068bf88e051a1436557addfffbbb0    sha256:da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e    io.containerd.runc.v2
1f717698484633c585f7bee3a2747c6db0944ffe0197f8177167e7ea1e6bde48    sha256:da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e    io.containerd.runc.v2
22d7e511d252bd22088210b2dcfd55cef742b868df196321edb9773e22931f09    sha256:da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e    io.containerd.runc.v2
29e98b39e98bc0c8b6897948b9704e3d8986720ba3c7a4c421a8673b5dd9ee92    sha256:4e797b3234604c31f729cb63b6128b623e2f76e629d53ccb84d899de4e73f759    io.containerd.runc.v2
2d673abe3c5b22492931e896d12eb9891a0d6ea6f9098a651e51358ba39d0d4f    sha256:da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e    io.containerd.runc.v2
3a771d947a5ebfc9a1a40fa514b3de63a2cdf110a735fd3cc5f9dd6ae5b5d47c    sha256:da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e    io.containerd.runc.v2
405a47aa4415269d606c90151eaf30e8e1df6eeed5389a88875260527935721a    sha256:da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e    io.containerd.runc.v2
4ca269034d9429fcb369cd41a6d0e0f0b066dd33e1b8920928630ec4389bf5f1    sha256:da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e    io.containerd.runc.v2
52752ba6db761c94a0e8781b1205505c91a20ebd24829e71e8efd09604327125    sha256:da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e    io.containerd.runc.v2
542db3877efb05e661e3b839730d3a7611c699cd38b3f79f30152ca9e4656c68    sha256:da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e    io.containerd.runc.v2
565286e4eab85d2d79a96d79694a1694172817b046ede891459badc1830a175f    sha256:da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e    io.containerd.runc.v2
59c35154a4401ae1032d5a73df1d58112386a64efaa504edcd2cbeae407ca6be    sha256:da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e    io.containerd.runc.v2
60f5a03cf4f929d904af87faf3f05843bbb3988f816435238835526281318526    sha256:da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e    io.containerd.runc.v2
7368e3384dc0e977ba45c10f991e1f1ac79c2638947f236357a1434ef0b7eca3    sha256:da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e    io.containerd.runc.v2
88694630e09c9f79edae338fa9ebfcca250a9287ef0bf760c4b6f8ba29500974    sha256:da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e    io.containerd.runc.v2
acd5df80ee3e5f6bd0eec05967e5c3d9ccf2d85d5b9d58035ea57a1e2d4dbdc6    sha256:da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e    io.containerd.runc.v2
c35de9e2af01c5b19a739f2114057bc7680358396e916acae94bf42694b59423    sha256:da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e    io.containerd.runc.v2
d0002983b72cc84787c254fe062cb379b3d4531f481d8dad9dedd6061d01af57    sha256:da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e    io.containerd.runc.v2
d01ed0ac4b35a9cfd628cb45a241958c5cf0f77ac900ae01d53cb9f6faef38da    sha256:da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e    io.containerd.runc.v2
da62bd025b86e38bc0f4db659dc480dd40d74fc1c6d284d00c448d1b2e221ab6    sha256:da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e    io.containerd.runc.v2
e4c72e5c0451562bc94aeb39436b30c1240deb2cadf6194797219d03fbcf43ee    sha256:da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e    io.containerd.runc.v2
e5a142d020f98f47d69d047e8b417badfdec7bb87f66c44642311e0748780c6a    sha256:da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e    io.containerd.runc.v2
e7e58105c9919aa056c1105f08b95d911564fcc75765dd7935ffc48e287dbdd2    sha256:da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e    io.containerd.runc.v2
ee6dd1996bd374140e5322343affcd54c6691cff51aef2957610004114412a2a    sha256:da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e    io.containerd.runc.v2
f6568a493a1d78eeec8fc2120c57ea457c090ebaa01bdda49feb8e65da243721    sha256:da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e    io.containerd.runc.v2
fc2395ec0c0e43181f16ac5a5c3a7ca73ac4c2244d434079746165a0dce7cad8    sha256:da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e    io.containerd.runc.v2

We can see that the image maps to the docker.io/rancher/pause:3.1 image.
[root@localhost ~]# k3s ctr image list | grep sha256:da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e
sha256:da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e                                   application/vnd.docker.distribution.manifest.list.v2+json sha256:d22591b61e9c2b52aecbf07106d5db313c4f178e404d660b32517b18fcbf0144 318.9 KiB linux/amd64,linux/arm,linux/arm64                           io.cri-containerd.image=managed

[root@localhost ~]# k3s crictl image ls  | grep da86e6b
docker.io/rancher/pause             3.1                 da86e6ba6ca19       327kB

When matching this with my previous comment, it seems that something SELinux related is not set up correctly yet for that image.
type=AVC msg=audit(1598524830.002:766834): avc:  denied  { read execute } for  pid=2434 comm="pause" path="/pause" dev="sda1" ino=67634416 scontext=system_u:system_r:container_t:s0:c541,c744 tcontext=unconfined_u:object_r:var_lib_t:s0 tclass=file permissive=0

When looking through journalctl we can also see that that SELinux error is related to /pause.
However the /pause file is not available on the filesystem, since it is used in a container.
[root@localhost ~]# journalctl -b -0
....
Aug 27 11:41:21 localhost.localdomain kernel: SELinux: mount invalid.  Same superblock, different security settings for (dev mqueue, type mqueue)
Aug 27 11:41:21 localhost.localdomain setroubleshoot[4550]: SELinux is preventing /pause from 'read, execute' accesses on the file /pause. For complete SELinux messages run: sealert -l 00838093-401f-4614-b585-af900140deb6
Aug 27 11:41:21 localhost.localdomain python[4550]: SELinux is preventing /pause from 'read, execute' accesses on the file /pause.

                                                    *****  Plugin restorecon (99.5 confidence) suggests   ************************

                                                    If you want to fix the label.
                                                    /pause default label should be etc_runtime_t.
                                                    Then you can run restorecon. The access attempt may have been stopped due to insufficient permissions to access a parent directory in which case try to change the following command accordingly.
                                                    Do
                                                    # /sbin/restorecon -v /pause

                                                    *****  Plugin catchall (1.49 confidence) suggests   **************************

                                                    If you believe that pause should be allowed read execute access on the pause file by default.
                                                    Then you should report this as a bug.
                                                    You can generate a local policy module to allow this access.
                                                    Do
                                                    allow this access for now by executing:
                                                    # ausearch -c 'pause' --raw | audit2allow -M my-pause
                                                    # semodule -i my-pause.pp

I was able to work around the SELinux problem related to the '/pause' file, which is used in the 'docker.io/rancher/pause' image by running the following:
[root@localhost ~]# ausearch -c 'pause' --raw | audit2allow -M my-pause
[root@localhost ~]# semodule -i my-pause.pp

Although I am not sure why I had to do this manually after installing the following required SELinux pacakges...

container-selinux
selinux-policy-base
https://rpm.rancher.io/k3s-selinux-0.1.1-rc1.el7.noarch.rpm

Just to make this issue complete, it seemed that there were 2 events related to the pause command.
[root@localhost ~]# ausearch -c 'pause'
...
----
time->Thu Aug 27 13:03:41 2020
type=ANOM_ABEND msg=audit(1598533421.490:247073): auid=1000 uid=0 gid=0 ses=3 subj=system_u:system_r:container_t:s0:c185,c332 pid=13246 comm="pause" reason="memory violation" sig=11
----
time->Thu Aug 27 13:03:43 2020
type=PROCTITLE msg=audit(1598533423.175:247269): proctitle="(null)"
type=SYSCALL msg=audit(1598533423.175:247269): arch=c000003e syscall=59 success=no exit=-13 a0=c000167a20 a1=c0001514d0 a2=c0001651a0 a3=0 items=0 ppid=14081 pid=14101 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=3 comm="pause" exe="/pause" subj=system_u:system_r:container_t:s0:c380,c863 key=(null)
type=AVC msg=audit(1598533423.175:247269): avc:  denied  { read execute } for  pid=14101 comm="pause" path="/pause" dev="sda1" ino=67634416 scontext=system_u:system_r:container_t:s0:c380,c863 tcontext=unconfined_u:object_r:var_lib_t:s0 tclass=file permissive=0
----
...

As you've noticed, it's a fair bit of work to try to repair a system that's been brought up without the correct packages and policies available. It's even more work to try do to it without simply deleting everything and starting over.
@davidnuzik I suggest that we handle this as a documentation issue - the install script checks for this and prevents users from starting k3s without the selinux policies in place, but users that want to drop the binary directly without using the script (or RPM) should be responsible for ensuring that this is done themselves.

I am also able to reproduce SELinux issues when defining a custom 'data-dir' path.
[root@localhost ~]# yum list installed | grep selinux
container-selinux.noarch            2:2.119.2-1.911c772.el7_8  @extras
k3s-selinux.noarch                  0.1.1-rc1.el7              @/k3s-selinux-0.1.1-rc1.el7.noarch
libselinux.x86_64                   2.5-15.el7                 @anaconda
libselinux-python.x86_64            2.5-15.el7                 @anaconda
libselinux-utils.x86_64             2.5-15.el7                 @anaconda
selinux-policy.noarch               3.13.1-266.el7_8.1         @updates
selinux-policy-targeted.noarch      3.13.1-266.el7_8.1         @updates

[root@localhost ~]# mkdir -p /mnt/data/kubernetes/
[root@localhost ~]# ls -ldZ  /mnt/data/kubernetes/
drwxr-xr-x. root root unconfined_u:object_r:mnt_t:s0   /mnt/data/kubernetes/

[root@localhost ~]# k3s server --data-dir=/mnt/data/kubernetes/ --no-deploy=metrics-server,traefik,servicelb,local-storage

In journalctl the following error message is shown related to SELinux.
Aug 28 07:54:26 localhost.localdomain setroubleshoot[4412]: SELinux is preventing /pause from 'read, execute' accesses on the file /pause. For complete SELinux messages run: sealert -l bf37dffe-0acb-4101-8cd7-1a23e9f7b560

[root@localhost ~]# sealert -l bf37dffe-0acb-4101-8cd7-1a23e9f7b560
SELinux is preventing /pause from 'read, execute' accesses on the file /pause.

*****  Plugin restorecon (99.5 confidence) suggests   ************************

If you want to fix the label.
/pause default label should be etc_runtime_t.
Then you can run restorecon. The access attempt may have been stopped due to insufficient permissions to access a parent directory in which case try to change the following command accordingly.
Do
# /sbin/restorecon -v /pause

*****  Plugin catchall (1.49 confidence) suggests   **************************

If you believe that pause should be allowed read execute access on the pause file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# ausearch -c 'pause' --raw | audit2allow -M my-pause
# semodule -i my-pause.pp

Additional Information:
Source Context                system_u:system_r:container_t:s0:c34,c437
Target Context                unconfined_u:object_r:mnt_t:s0
Target Objects                /pause [ file ]
Source                        pause
Source Path                   /pause
Port                          <Unknown>
Host                          localhost.localdomain
Source RPM Packages
Target RPM Packages
Policy RPM                    selinux-policy-3.13.1-266.el7_8.1.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     localhost.localdomain
Platform                      Linux localhost.localdomain 3.10.0-1127.el7.x86_64
                              #1 SMP Tue Mar 31 23:36:51 UTC 2020 x86_64 x86_64
Alert Count                   1
First Seen                    2020-08-28 07:54:25 UTC
Last Seen                     2020-08-28 07:54:25 UTC
Local ID                      bf37dffe-0acb-4101-8cd7-1a23e9f7b560

Raw Audit Messages
type=AVC msg=audit(1598601265.883:1160): avc:  denied  { read execute } for  pid=4922 comm="pause" path="/pause" dev="sda1" ino=33586703 scontext=system_u:system_r:container_t:s0:c34,c437 tcontext=unconfined_u:object_r:mnt_t:s0 tclass=file permissive=0

type=SYSCALL msg=audit(1598601265.883:1160): arch=x86_64 syscall=execve success=no exit=EACCES a0=c0000a1a50 a1=c00010eba0 a2=c0000971a0 a3=0 items=0 ppid=4902 pid=4922 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4 comm=pause exe=/pause subj=system_u:system_r:container_t:s0:c34,c437 key=(null)

Hash: pause,container_t,mnt_t,file,read,execute

Adding a custom module for all 'pause' SELinux alerts works around the issue.
[root@localhost ~]# ausearch -c 'pause' --raw | audit2allow -M my-pause
[root@localhost ~]# semodule -i my-pause.pp

After solving the 'pause' issue, the next SELinux related alert pops up.
Aug 28 07:56:49 localhost.localdomain setroubleshoot[24296]: failed to retrieve rpm info for /etc/resolv.conf
Aug 28 07:56:49 localhost.localdomain setroubleshoot[24296]: SELinux is preventing /coredns from open access on the file /etc/resolv.conf. For complete SELinux messages run: sealert -l fe3663c0-08c4-48cd-a765-eecd4b455b19

Again, by creating a custom module you can work around the issue.
[root@localhost ~]# ausearch -c 'coredns' --raw | audit2allow -M my-coredns
[root@localhost ~]# semodule -i my-coredns.pp

After these two manual actions, k3s is running properly with a custom data directory.
This can also be replicated by using the k3s install script.
It seems using the '--data-dir' k3s argument is not supported when enabling k3s?

The install script does not validate or take any action on the flags; they're passed through to the service as-is. Setting the correct context on the data-dir (whether default or custom) would definitely be part of the documentation for manual installs with selinux.

Documentation for how we'll recommend a k3s install on selinux-enforcing system to be handled here: https://github.com/rancher/k3s/issues/2058
The plan will be to support the yum repo installation method.

I believe this should be covered in the documentation now.


Update how-to-train-cli.md

@AbeOmor : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@AbeOmor : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


fix: flame-bloc : Remove final keyword from subscription in FlameBlocListenable

Description
Correct a late initialization error that occurs when re-visiting a route previous visited that is using the FlameBlocListenable mixin.  The final keyword is remove from _subscription field declaration so that the error does not occur on subsequent mounts of the component.
Checklist

[X] The title of my PR starts with a Conventional Commit prefix (fix:, feat:, docs: etc).
[X] I have followed the Contributor Guide when preparing my PR.
[-] I have updated/added tests for ALL new/updated/fixed functionality.
[-] I have updated/added relevant documentation in docs and added dartdoc comments with ///.
[-] I have updated/added relevant examples in examples or docs.

Breaking Change?

[ ] Yes, this PR is a breaking change.
[X] No, this PR is not a breaking change.

Related Issues

Could you add a small test that tests that it now works to re-visit a route?

@spydon - I have added a test to flame_bloc_listenable_test for this.  Thanks!!!

Thanks for this fix @pastordougdev 🎉
@spydon and @erickzanardo when can we expect the next pub release for flame_bloc?


Use type from @graphql-typed-document-node/core

This project is so helpful - thank you for making it!
I wanted to suggest switching the type exported from generated code to the TypedDocumentNode type from the @graphql-typed-document-node/core package. The reason is that Apollo Client, and possibly other libraries, accept this type, and correctly propagate types for result data, and for variables. IMO that makes @graphql-typed-document-node/core a sort of standard for typed queries. If you use it then queries typed by @ts-gql could be used in other contexts without custom wrappers to match up types.
The definition from @graphql-typed-document-node/core looks like this:
import { DocumentNode } from 'graphql';
export interface TypedDocumentNode<Result = {
    [key: string]: any;
}, Variables = {
    [key: string]: any;
}> extends DocumentNode {
    __resultType?: Result;
    __variablesType?: Variables;
}
/**
 * Helper for extracting a TypeScript type for operation result from a TypedDocumentNode.
 * @example
 * const myQuery = { ... }; // TypedDocumentNode<R, V>
 * type ResultType = ResultOf<typeof myQuery>; // Now it's R
 */
export declare type ResultOf<T> = T extends TypedDocumentNode<infer ResultType, infer VariablesType> ? ResultType : never;
/**
 * Helper for extracting a TypeScript type for operation variables from a TypedDocumentNode.
 * @example
 * const myQuery = { ... }; // TypedDocumentNode<R, V>
 * type VariablesType = ResultOf<typeof myQuery>; // Now it's V
 */
export declare type VariablesOf<T> = T extends TypedDocumentNode<infer ResultType, infer VariablesType> ? VariablesType : never;

Happy to accept a PR that makes ts-gql's TypedDocumentNode intersect with the one from @graphql-typed-document-node/core though there are some things that @graphql-typed-document-node/core wouldn't support(typing of refetchQueries with the specific queries that are available) so I'd rather not switch completely.


How to use with LXD

Hi if I understand correctly the config of a container is in YAML format.
lxc edit config <container name>
Takes me to a yaml file and I have no Idea how to add your script to it.

LXD is not supported and will not be supported by this script. They have solved the same problem with a user-space helper called "proxy".


ENH: Write a simples 'eval' function

Seems to me that is unnecessary to expose the process
input -> lexer -> tokens -> parser -> tree -> interpreter -> output
to user.
The library should have a default evaluation function.

Nice idea. The library can expose it through lib.lexer, but it would be useful to have a simple function.
evaluate?
solve?
calc?

calculate

@hsguidi, I assign it to you, as discussed on #30 .


allow users to delete or hide resources they created

Describe the feature you'd like
allow user to delete or hide a resources, including templates.
for templates, it might be better to have a way to hide them vs delete them, in case resources were created based on them.
for all resources, probably want to restrict this that you can't hide or delete something unless you (or someone else in your group) created it
Give an example
i made a template as an experiment, but don't need it anymore. i want to delete or hide it so that the list of templates isn't clogged with unused templates
Describe alternatives you've considered
currently a user has to open a ticket and request deletion of a resource
A clear and concise description of any alternative solutions or features you've considered.
an alternative could be to have a few superuser/admin user types (not developers) who have the power and training to delete things, and other users could make a request for deletions

+1


Simplify README.md using the wiki

See #517
Changes:

moved most of the service list into the wiki
made existing examples simpler and more complete
swapped some sections to highlight the main features of the package
added several links to the wiki

Added wiki without PR after CGNonofr approval in #517 , since Wikis do not follow the Github Workflow.

Big Thank you! It looks good as a starting point


TypeScript intellisense does not work correctly for interface properties that can be an interface or an array of interfaces

VSCode Version: 1.8.0
OS Version: Linux Mint 17 Xfce 64-bit

TypeScript intellisense does not work correctly on interface properties that can be an interface or an array of that interface. Intellisense is only present when the property is in the array form.
Code to reproduce:
interface SomeInterface {
    prop1: number;
    prop2: string;
}
interface ComplexInterface {
    fail: SomeInterface | SomeInterface[];
}
let b:ComplexInterface = {
    fail: {}
}

Screenshot of what intellisense gives if the property is an object:

Screenshot of what intellisense gives if the property is an array of objects:

Expected behavior is that intellisense in the first screenshot would act like the second screenshot, and list properties prop1 and prop2.
Edit: I found that if I use fail: <SomeInterface>{}, intellisense works as expected, as shown in the below screenshot. However, this seems like it shouldn't be necessary, given how good TypeScript is at inferring other things.

This issue was moved to Microsoft/TypeScript#13036


Allow the user to redefine nonFatal classes

In some cases we may want to consider some exceptions as critical and let the code crash
In some cases we have to integrate with badly written libraries which are using fatal exceptions to signal about their issues. In my case it was UnknownError
In some rare cases we may want to handle VM errors. In my case I've been handling OOMs to trigger a chunk of native code through JNI.

Related: #173
@jmcardon please look.

@pshirshov I am tempted to delete NonFatal entirely and catch all errors. Would that be equivalent or do you prefer a custom NonFatal handler?

But why? There's literally syncthrowable for this!

Depends on your situation. I agree on the argument about improper usage and don't agree on the argument about broken state where you need to try to do something (pass execution to native code) but the vm can't continue to work.

@jmcardon
The point is being able e.g. immediately kill the VM with System.exit() on OutOfMemory exception to prevent additional allocations on shutdown and potential total freeze.
I can't describe how completely unrelated syncThrowable is for this case.

@jmcardon A simple argument for having this customizable (or deleting it entirely) is that no two libraries agree on the set of NonFatal throwables.
My own personal preference is to catch everything because all the other libraries are broken anyway (for example, performing heap allocation on fatal exceptions!!!), and in general everything about the runtime is undefined after a truly fatal exception, so who cares whether you catch or not (in some cases you may make enough progress to log something useful or shutdown somewhat more cleanly).

My P/R doesn't make things worse but makes them better - behavior is exactly the same as it is right now but you may alter it. So I don't know what may be an objection for this :(

@pshirshov I'm inclined to agree about your PR since it just moves nonFatal to RTS which is perhaps a better place for it anyway. We need the build to pass though. 😄

Build failed bcs of microsite generator I guess. Ok, I will rebase.

@jdegoes , @NeQuissimus : at the moment the build is broken by a line from my other P/R:
The command "if [[ "$TRAVIS_PULL_REQUEST" = "false" ]] ; then sbt ++$TRAVIS_SCALA_VERSION sonatypeRelease ; fi" exited with 1.

Someone need to drop all the old unclosed staging repositories from sonatype.

I can drop the staging artifacts when I am home. Can you send a PR with the key stuff?


Zoomify and Controlify mods cannot start together because of a Quilted Fabric API quirk

Relevant issue at the other end: https://github.com/isXander/Zoomify/issues/195
It seems as though the version parse method used by Quilt is ever so slightly different to induce some mods' code into behaving erratically.
Relevant calls:
https://github.com/isXander/Zoomify/blob/1.20/src/main/kotlin/dev/isxander/zoomify/integrations/IntegrationHelper.kt

QFAPI has nothing to do with this.
This is an issue with Quilt Loader itself.


Clean up logging and dry run setting for vaccination emails.

Remove noisy logs that were for debugging.
Fix logs to log location names instead of FIPS.
Tweak github workflow to have a "send emails" option instead of "dry run"
option to be more similar to risk alerts.

https://trello.com/c/gS9cOyG3/1030-vaccine-emails-dryrun-state-abbr-instead-of-fips-in-summary

 Vaccine Emails Dryrun State Abbr instead of Fips in Summary


Add Profile requirements to HydroShare new user steps

Currently, new HydroShare users are only required to put their first and last name.   This leads to what I call the 'Empty Profile Problem' which makes social functions or use tracking severely limiting (see use tracking reporting by @Castronova ).
The Education & Outreach group has come to a consensus that adding the requirement to fill 'Institution' and 'Title' adds sufficient benefits without significantly slowing down the workshop and introduction process for new users.
Thanks!!

We also need to think about using controlled lists for the Title and Institution so it is more easy for Kibana and @Castronova  to do useful work with the Profile info.
Would also be nice to have an option where someone signing up at an event, or by referral , could volunteer the information, so that @Castronova can track where the users came from.
Thanks!
C

@aphelionz Should @mauriel133 work on this?

Hi All,
What is the timeline to update this feature?  Thanks!
Christina

Thanks Mauriel!!  Let me know if/when you want help with testing.
C

@ChristinaB, do you have curated lists for Title and Organization or are these going to be self updating (by providing the option to input new values and adding to the list)?

The tracking for organization had already been implemented here:
https://github.com/hydroshare/hydroshare/pull/1303/commits/10738fa5c5a8fbeca2ed5d8c9325bd12f90d8f45
@jbradberry, it looks like this work didn't make it into development. Is it in some other branch?

@mauriel133 According to https://github.com/hydroshare/hydroshare/pull/1303#issuecomment-270412686 , this work was copied elsewhere and merged.  However, I haven't been on this project for months now, so I have no first-hand knowledge that this is the case.

@pkdash, it looks like this work (https://github.com/hydroshare/hydroshare/pull/1303) didn't make it into the development branch. Who would be a good candidate to bring these back end changes into our current development branch?

@mauriel133 I guess @aphelionz or @hyi can help on this. Is this functionality needed for release 1.10? The RC for release 1.10 supposed to come out on Wednesday.

@pkdash,
Yes, this is needed for release 1.10. The work that was done in that PR implements the Organization field as a self-updating autocomplete list. It also implement other important constraints on tracked fields.

Thanks for your work on this @Maurier !!

I tested this on beta and it is not implemented.  Any chance we can sneak it in 1.10?

see prt #1303

@rayi113 @ChristinaB @dtarb
Do we want highest level of education as a required field here or will we nag them about it with the notification... or will we do nothing? let me know.

Required would be great as this information is used for reporting purposes, however if we do require this we may additionally need an option like "Prefer not to disclose" in addition to how these options are usually stated.  Defer to @dtarb  for ultimate decision on this.

@aphelionz - can you check in with @Maurier ? He can work on the front end changes needed for adding education level to the profile, but he wanted to know who could help him out with the back end stuff.

@horsburgh @Maurier
I was able to cherry pick the commit you mentioned to get the organizations field. I'm planning on doing the rest, is that ok?

Fine with me. @Maurier ?

Yes, sounds good.

Removing @Maurier from this one since it looks like @aphelionz is taking care of it.

I believe this ticket has been satisfied. Please re-open or make a new ticket if that is not the case
cc @horsburgh @ChristinaB


Strategy to automate new datasets version download

Data providers have various ways to propose their file download, hence the grabbing the new version of a dataset can be tricky.

The simplest case is when the file URL doesn't change, so we just need to check for the file modification date in the HEADER (e.g. HGNC, some providers offers an URL with /latest)

Usually a new file/directory with the new version name is created for the files. See stitch, string, e.g. protein.links.v10.5.txt.gz become protein.links.v11.0.txt.gz

This could be resolved by parsing the HTML of the download page or going through the FTP directories. And using regex to get the new file with the version
A strategy here to be able to automatically download new versions would be to get the HTML, parse it using Jsoup, execute regex, get new files URL (careful the URL might be relative in the HTML)
Note that at the moment the worst case encountered is 2 step HTML parsing with regex (first to get the directories, then the files)
Should the d2s-download module generate RDF to capture some informations about the download? (HCLS)

Now using https://github.com/MaastrichtU-IDS/d2s-bash-exec to easily provide download bash scripts to execute

Done through the d2s client


Add links doesn't work unless the file already exists

Ideally the command should create any files that don't exist, currently you have to ctrl+click each link first to create the file and then execute the command

"Add links" command should add external URLs as well as internal links. Recently found out that it doesn't.


Automated Release Build and Publishing

This PR introduces a GitHub Actions workflow. When you publish a new GitHub release, this workflow...

takes the version number from the release tag, for example "v1.4.0dev1".
injects that version into setup.py and pypyodbc.py.
builds a source archive and a py3 wheel, which is cross-platform.

The version number is part of the file names.

uploads both artifacts to the GitHub release.
depending on the version number...

If the version contains "dev", as in the example above, nothing further happens.

For developmental releases.
Example release and build log.

If the version contains "a" or "b", for example v1.4.0a2, both artifacts are published to Test PyPI.

For alpha and beta pre-releases.
Example release and build log.

Otherwise, both artifacts are published to PyPI proper.

For rc and final releases.
Example release and build log.
Upload to PyPI failed intentionally, as I don't have permission to yank or delete a release.
But the upload script was tested with a dummy project against PyPI, too.

The major change to the codebase is that I've removed the "next" version number from pypyodbc.py and instead put a placeholder there, and into setup.py. That placeholder is searched and replaced by the version injection script. @braian87b if you move the versions to another file, for example from setup.py to setup.cfg, you'll have to update .github/scripts/inject-version.sh accordingly. The line with the sed command at the end.
I had to remove the import of pypyodbc from setup.py to make the build work, and instead duplicated the version placeholder. On import, pypyodbc tries to load libodbc. But that library may not available in the build environment, where setup.py is evaluated. With the version number being injected automatically, there's no concern about differing version numbers in two places anymore.
I removed the test_version functions from two files. It would only test the placeholder, but not the actual version that's injected at build time.
There are some moving pieces in the workflow. It uses GitHub's latest Ubuntu image, where the python3 version may change. It installs the latest version of build for building the packages, and of twine for uploading to (test) PyPI. If there is a new release after a longer break, I recommend to first make a developmental release (for testing the build step), then an alpha release (for testing the publishing step).

When #14 gets merged, the .gitignore file here should be dropped. The one from #14 covers everything.

@braian87b The two approaches for getting repository secrets in place are:

You do it.
You make me an administrator, so that I can do it.

No need to hurry a decision. I won't find time in the near future anyway to resolve the conflicts. Maybe in summer.


[WIP] Mode dashboard owner

Summary of Changes
Include a summary of changes then remove this line
Tests
What tests did you add or modify and why? If no tests were added or modified, explain why. Remove this line
Documentation
What documentation did you add or modify and why? Add any relevant links then remove this line
CheckList
Make sure you have checked all steps below to ensure a timely review.

[ ] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[ ] PR includes a summary of changes.
[ ] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[ ] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain docstrings that explain what it does

[ ] PR passes make test

Codecov Report

Merging #200 into master will decrease coverage by 1.23%.
The diff coverage is 7.93%.

@@            Coverage Diff             @@
##           master     #200      +/-   ##
==========================================
- Coverage   80.18%   78.95%   -1.24%
==========================================
  Files          79       82       +3
  Lines        3669     3730      +61
  Branches      391      391
==========================================
+ Hits         2942     2945       +3
- Misses        616      674      +58
  Partials      111      111

Impacted Files
Coverage Δ

databuilder/models/dashboard/dashboard_owner.py
0% <0%> (ø)

...d/mode_analytics/mode_dashboard_owner_extractor.py
0% <0%> (ø)

databuilder/models/owner_constants.py
100% <100%> (ø)

databuilder/models/table_owner.py
77.27% <100%> (+0.52%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6c4bd0b...a0d4e95. Read the comment docs.

Codecov Report

Merging #200 into master will decrease coverage by 0.61%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #200      +/-   ##
==========================================
- Coverage   80.18%   79.57%   -0.62%
==========================================
  Files          79       82       +3
  Lines        3669     3730      +61
  Branches      391      375      -16
==========================================
+ Hits         2942     2968      +26
- Misses        616      648      +32
- Partials      111      114       +3

Impacted Files
Coverage Δ

...ilder/transformer/regex_str_replace_transformer.py
95.83% <0.00%> (-4.17%)
:arrow_down:

...abuilder/extractor/snowflake_metadata_extractor.py
93.44% <0.00%> (-1.64%)
:arrow_down:

...tabuilder/extractor/postgres_metadata_extractor.py
93.54% <0.00%> (-1.62%)
:arrow_down:

databuilder/publisher/neo4j_csv_publisher.py
84.15% <0.00%> (-1.00%)
:arrow_down:

databuilder/task/neo4j_staleness_removal_task.py
56.98% <0.00%> (ø)
:arrow_up:

...d/mode_analytics/mode_dashboard_owner_extractor.py
0.00% <0.00%> (ø)

databuilder/models/dashboard/dashboard_owner.py
89.65% <0.00%> (ø)

databuilder/models/owner_constants.py
100.00% <0.00%> (ø)

databuilder/models/user.py
86.30% <0.00%> (+2.73%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6c4bd0b...396ec65. Read the comment docs.

Codecov Report

Merging #200 into master will decrease coverage by 0.48%.
The diff coverage is 49.2%.

@@            Coverage Diff            @@
##           master    #200      +/-   ##
=========================================
- Coverage   80.18%   79.7%   -0.49%
=========================================
  Files          79      82       +3
  Lines        3669    3730      +61
  Branches      391     391
=========================================
+ Hits         2942    2973      +31
- Misses        616     646      +30
  Partials      111     111

Impacted Files
Coverage Δ

...d/mode_analytics/mode_dashboard_owner_extractor.py
0% <0%> (ø)

databuilder/models/owner_constants.py
100% <100%> (ø)

databuilder/models/table_owner.py
77.27% <100%> (+0.52%)
:arrow_up:

databuilder/models/dashboard/dashboard_owner.py
89.65% <89.65%> (ø)

databuilder/models/user.py
86.3% <0%> (+2.73%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6c4bd0b...396ec65. Read the comment docs.

Codecov Report

Merging #200 into master will decrease coverage by 0.97%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #200      +/-   ##
==========================================
- Coverage   80.18%   79.21%   -0.98%
==========================================
  Files          79       83       +4
  Lines        3669     3757      +88
  Branches      391      396       +5
==========================================
+ Hits         2942     2976      +34
- Misses        616      669      +53
- Partials      111      112       +1

Impacted Files
Coverage Δ

databuilder/models/owner_constants.py
100.00% <0.00%> (ø)

databuilder/models/dashboard/dashboard_owner.py
89.65% <0.00%> (ø)

databuilder/rest_api/rest_api_error_handlers.py
0.00% <0.00%> (ø)

...d/mode_analytics/mode_dashboard_owner_extractor.py
0.00% <0.00%> (ø)

databuilder/models/user.py
86.30% <0.00%> (+2.73%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6c4bd0b...bcf1af2. Read the comment docs.

Codecov Report

Merging #200 into master will decrease coverage by 0.97%.
The diff coverage is 40.42%.

@@            Coverage Diff             @@
##           master     #200      +/-   ##
==========================================
- Coverage   80.18%   79.21%   -0.98%
==========================================
  Files          79       83       +4
  Lines        3669     3757      +88
  Branches      391      396       +5
==========================================
+ Hits         2942     2976      +34
- Misses        616      669      +53
- Partials      111      112       +1

Impacted Files
Coverage Δ

...d/mode_analytics/mode_dashboard_owner_extractor.py
0% <0%> (ø)

databuilder/rest_api/rest_api_error_handlers.py
0% <0%> (ø)

databuilder/models/owner_constants.py
100% <100%> (ø)

databuilder/models/table_owner.py
77.27% <100%> (+0.52%)
:arrow_up:

databuilder/rest_api/rest_api_query.py
76.25% <50%> (-6.61%)
:arrow_down:

databuilder/models/dashboard/dashboard_owner.py
89.65% <89.65%> (ø)

... and 1 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6c4bd0b...bcf1af2. Read the comment docs.

Um, any idea why codecov is commenting through my account?!

Um, any idea why codecov is commenting through my account?!

I have no idea. Are you getting this from other PRs as well?

Yes, on different repos:
https://github.com/lyft/amundsensearchlibrary/pull/70#issuecomment-591174592
https://github.com/lyft/amundsenfrontendlibrary/pull/366#issuecomment-591166790

is codecov account shared somehow? I can't think of any of reasons how this happens...

@feng-tao Just updated A -> An 😄
Could you approve again?


third-party package is falsely required to export package.json

Describe the bug
I am using the p-limit package which throws the following warning when building with SvelteKit:
[vite-plugin-svelte] The following packages did not export their `package.json` file so we could not check the "svelte" field. If you had difficulties importing svelte components from a package, then please contact the author and ask them to export the package.json file.
- p-limit
- yocto-queue

According to the owner of the package, this is a mistake on the end of vite-plugin-svelte: https://github.com/sindresorhus/p-limit/issues/62
Reproduction

install p-limit package
use it in code
run pnpm build in a SvelteKit starter template
expect warning to pop up

Logs
No response
System Info
System:
    OS: Linux 5.16 Manjaro Linux
    CPU: (8) x64 Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz
    Memory: 6.71 GB / 15.61 GB
    Container: Yes
    Shell: 5.8.1 - /bin/zsh
Binaries:
    Node: 16.14.1 - ~/.volta/tools/image/node/16.14.1/bin/node
    Yarn: 1.22.17 - ~/.volta/tools/image/yarn/1.22.17/bin/yarn
    npm: 8.5.0 - ~/.volta/tools/image/node/16.14.1/bin/npm
Browsers:
    Brave Browser: unknown
    Firefox: 98.0.1
npmPackages:
    @sveltejs/adapter-static: 1.0.0-next.29 => 1.0.0-next.29
    @sveltejs/kit: 1.0.0-next.299 => 1.0.0-next.299
    svelte: ^3.46.4 => 3.46.4

Severity
annoyance

We've removed the warning since https://github.com/sveltejs/vite-plugin-svelte/pull/272. Are you on the latest version of vite-plugin-svelte?

I used @sveltejs/kit/1.0.0-next.299 which required @sveltejs/vite-plugin-svelte': 1.0.0-next.34
Upgrading to @sveltejs/kit/1.0.0-next.302 pulled in @sveltejs/vite-plugin-svelte': 1.0.0-next.40 which indeed removed the warning ;)
Thanks!


[Bug] [8.5.0] [iOS] Firestore crash when snapshot listener being used

[REQUIRED] Please fill in the following fields:

Unity editor version: 2020.3.5f1
Firebase Unity SDK version: 8.5.0
Source you installed the SDK: Local .tgz
Problematic Firebase Component: Firestore
Other Firebase Components in use: Everything
Additional SDKs you are using: Facebook, Apple Sign In, Google Sign In, Unity Ads, Unity Purchasing
Platform you are using the Unity editor on: Mac M1
Platform you are targeting: iOS
Scripting Runtime: IL2CPP

[REQUIRED] Please describe the issue here:
The app crashes on iOS during my ListenServerVersion() function call.
The function is listening for a Firestore snapshot.
This has only started happening as of 8.5.0. It was working fine in previous versions.
Steps to reproduce:
Try to listen to a document snapshot during the firebase startup dependency check.
Relevant Code:
This is the startup code. The problematic function is called near the end of the startup sequence.
void StartFirebase()
	{
		//Check Dependencies
		Firebase.FirebaseApp.CheckAndFixDependenciesAsync().ContinueWithOnMainThread(task =>
		{
			var dependencyStatus = task.Result;
			if (dependencyStatus == Firebase.DependencyStatus.Available)
			{
				//Dynamic Links
				DynamicLinks.DynamicLinkReceived += OnDynamicLink;

				//App Reference
				appRef = Firebase.FirebaseApp.DefaultInstance;

				//Authentication Reference
				authRef = Firebase.Auth.FirebaseAuth.DefaultInstance;

				//Firestore Reference
				firestoreRef = FirebaseFirestore.DefaultInstance;

				//Realtime Database Reference
				databaseRef = FirebaseDatabase.DefaultInstance;

				//Storage Reference
				storageRef = FirebaseStorage.DefaultInstance.RootReference;

				//Function Reference
				functionRef = FirebaseFunctions.DefaultInstance;

				//Get Remote Config Reference
				remoteConfigRef = Firebase.RemoteConfig.FirebaseRemoteConfig.DefaultInstance;

				//Set Initialized
				IsFirebaseInitialized = true;

				//Setup Remote Config
				SetupRemoteConfig();

				//Listen for Server Version
				ListenServerVersion();

				Debug.Log("Firebase Initialized!");
			}
			else
			{
				UnityEngine.Debug.LogError(System.String.Format(
					"Could not resolve all Firebase dependencies: {0}", dependencyStatus));
				// Firebase Unity SDK is not safe to use here.
			}
		});
	}

This is the function in question:
///Listen Server Version
	void ListenServerVersion()
	{
		DocumentReference docRef = firestoreRef.Collection("server").Document("info");
		versionListener = docRef.Listen(snapshot =>
		{
			//Get Snapshot
			Dictionary<string, object> dict = snapshot.ToDictionary();

			//Check Server Version
			int version = int.Parse(dict["version"].ToString());

			//Update State
			print("Check Server Version: " + version + " == " + SaveManager.ServerVersion);
			if (version == SaveManager.ServerVersion)
			{
				//Continue
				print("Server Version Verified!");
				IsFirebaseVerified = true;
				HideInfo();
			}
			else
			{
				print("Server Version Mismatch!");
				IsFirebaseVerified = false;
				ShowInfo(CuriousLocalization.GetLocalizedString("error-app-maintenance") + "\n" + CuriousLocalization.GetLocalizedString("error-app-update"), 0.5f);
				SaveManager.SplashSeen = false;
				LoadController.instance.LoadScene("Login");
			}
		});
	}

This is the log from xCode:
2021-11-03 11:42:13.041743-0600 DoodleParty[347:11616] WF: _WebFilterIsActive returning: NO
Unexpected exception thrown by DocumentSnapshotsHandler() when invoked by P/Invoke: System.NullReferenceException: Object reference not set to an instance of an object.
  at FirebaseManager.<ListenServerVersion>b__262_0 (Firebase.Firestore.DocumentSnapshot snapshot) [0x00000] in <00000000000000000000000000000000>:0
  at System.Action`1[T].Invoke (T obj) [0x00000] in <00000000000000000000000000000000>:0
  at Firebase.Firestore.DocumentReference+<Listen>c__AnonStorey0+<Listen>c__AnonStorey1.<>m__0 () [0x00000] in <00000000000000000000000000000000>:0
  at System.Func`1[TResult].Invoke () [0x00000] in <00000000000000000000000000000000>:0
  at Firebase.Dispatcher.Run[TResult] (System.Func`1[TResult] callback) [0x00000] in <00000000000000000000000000000000>:0
  at Firebase.Platform.FirebaseHandler.RunOnMainThread[TResult] (System.Func`1[TResult] f) [0x00000] in <00000000000000000000000000000000>:0
  at Firebase.Firestore.DocumentReference+<Listen>c__AnonStorey0.<>m__0 (Firebase.Firestore.DocumentSnapshotProxy snapshotProxy, Firebase.Firestore.FirestoreError errorCode, System.String errorMessage) [0x00000] in <00000000000000000000000000000000>:0
  at System.Action`3[T1,T2,T3].Invoke (T1 arg1, T2 arg2, T3 arg3) [0x00000] in <00000000000000000000000000000000>:0
  at Firebase.Firestore.DocumentReference.DocumentSnapshotsHandler (System.Int32 callbackId, System.IntPtr snapshotPtr, Firebase.Firestore.FirestoreError errorCode, System.String errorMessage) [0x00000] in <00000000000000000000000000000000>:0
  at Firebase.AppUtilPINVOKE.Firebase_App_PollCallbacks () [0x00000] in <00000000000000000000000000000000>:0
  at Firebase.AppUtil.PollCallbacks () [0x00000] in <00000000000000000000000000000000>:0
  at Firebase.Platform.FirebaseAppUtils.PollCallbacks () [0x00000] in <00000000000000000000000000000000>:0
  at Firebase.Platform.FirebaseHandler.Update () [0x00000] in <00000000000000000000000000000000>:0
  at Firebase.Platform.FirebaseMonoBehaviour.Update () [0x00000] in <00000000000000000000000000000000>:0
UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
UnityEngine.DebugLogHandler:LogFormat(LogType, Object, String, Object[])
UnityEngine.Logger:Log(LogType, Object)
UnityEngine.Debug:LogError(Object)
Firebase.Platform.FirebaseLogger:LogMessage(PlatformLogLevel, String)
Firebase.LogUtil:LogMessage(LogLevel, String)
Firebase.Firestore.Internal.Util:OnPInvokeManagedException(Exception, String)
Firebase.Firestore.DocumentReference:DocumentSnapshotsHandler(Int32, IntPtr, FirestoreError, String)
Firebase.AppUtilPINVOKE:Firebase_App_PollCallbacks()
Firebase.AppUtil:PollCallbacks()
Firebase.Platform.FirebaseAppUtils:PollCallbacks()
Firebase.Platform.FirebaseHandler:Update()
Firebase.Platform.FirebaseMonoBehaviour:Update()

Unfortunately, this is a known issue that snuck into the 8.5.0 release. We have a fix for it in the next release whose ETA is roughly 2 weeks from now. The only workaround is to downgrade the Unity SDK. Please see this duplicate issue for more details: https://github.com/firebase/quickstart-unity/issues/1171

The fix was just released in the Firebase Unity SDK 8.6.0.


updated factory creation example

as of nWidart/laravel-modules#1100 the factory generation command takes the model name as argument rather than the factory name
before php artisan module:make-factory PostFactory Blog
after php artisan module:make-factory Post Blog

Great, thanks!


Migrate this repository to the quickfeed organization

We should update all the import paths in this process as well.

See the description in transferring a repository.

[ ] Migrate the repository to the quickfeed organization
[ ] Update import paths
[ ] Update go.mod files
[ ] Update import paths and go.mod files using the kit module (dat320, dat520 and possibly others)

This has been completed. I've created issues on the dat320 and dat520 repositories to remind to update the import paths and fetch a new release (when we make a new release of the kit module.)


detection.py  No loop matching

Hi, thanks for your work.
when I running detection.py, I have an Error as below, could you give any advice?
Traceback (most recent call last):
File "/home/3D_detection-master/detection.py", line 83, in
points2D = gen_3D_box(yaw, dims, cam_to_img, box_2D)
File "/home/3D_detection-master/util/post_processing.py", line 112, in gen_3D_box
center = compute_center(points3D, rot_M, cam_to_img, box_2D, inds)
File "/home/3D_detection-master/util/post_processing.py", line 75, in compute_center
result = solve_least_squre(W, y)
File "/home/3D_detection-master/util/post_processing.py", line 28, in solve_least_squre
U, Sigma, VT = np.linalg.svd(W)
File "/home/.local/lib/python3.6/site-packages/numpy/linalg/linalg.py", line 1612, in svd
u, s, vh = gufunc(a, signature=signature, extobj=extobj)
TypeError: No loop matching the specified signature and casting
was found for ufunc svd_n_f

yes，i found the same problem. So do you slove this problem finally?

Have you solved this error?


Add reduced-collection-frequency for niche use case

to be documented
related to https://github.com/crossbeam-rs/crossbeam/issues/852

Couldn't this be added as a config option on Collector, and maybe make it atomic so the global collector's can be updated?


Remove runAsUser in mssql

Should prevent using the oc adm policy add-scc-to-group nonroot system:authenticated workaround for mssql which seems causing other issues.
Signed-off-by: Raul Sevilla<EMAIL_ADDRESS>

Results for ec2_jjb
No tests to run

/rerun all tests/test_hammerdb.sh

Results for ec2_jjb

Test
Result
Retries
Duration (HH:MM:SS)

test_hammerdb
Pass
0
00:03:57


Trouble handling exceptions

Hi guys,
This is not actually an issue but I’m struggling with exception handling for quite some time.
I get the error object perfectly with the .catch part but unfortunately the message string is somehow formatted and i can not get plain text from this.
The exception looks like:
[31mC:\Users\michalski\source\NodeJS\ServiceDeskBackend\PsScript\test.ps1 : Es wurde kein Parameter gefunden, der dem Parameternamen "x" entspricht.[39m [31mIn Zeile:1 Zeichen:41[39m [31m+ .\PsScript\test.ps1 -identity michalski -x test[39m [31m+ ~~[39m [31m + CategoryInfo : InvalidArgument: (:) [test.ps1], ParameterBindingException[39m [31m + FullyQualifiedErrorId : NamedParameterNotFound,test.ps1[39m [31m [39m [31m[39m"
It’s mainly about the [31m and [39m.
Anyone any idea how to format this properly without just regexing the [* away ?

@MichalskiM ,
Please take a look on this:
https://stackoverflow.com/a/15146516


chore(deployment): Move away from package variables.

Describe what should be investigated or refactored
As noted by @jeff-mccoy: https://github.com/defenseunicorns/leapfrogai/pull/275#pullrequestreview-1962203463
Package variables should be dropped to go with component composability

Closed


Sync key client implementation

This closes #5184, #5401
Replaced handwritten sync Keys client with a wrapper around the generated code.

Can one of the admins verify this patch?

@schaabs Java currently implements import_key. I wasn't sure if we wanted to implement it or not.


Github logo in the footer is not properly placed.

The way the github logo is just peaking above the fold is an intentional design choice.