Mikhael
Mikhael
Hello, any update on this?
just encountered this error too, need help.
Fixed after rebooting. I don't know what makes this node needs to be rebooted when similar nodes does not need to be rebooted.
I was installing a microk8s on 2 VM. This happened on the second VM. The first VM installs smoothly. VM is same, with the only different is the IPs. A...
After chmod 777 on /mnt/, some of the pods start to work normally. Idk how this fixed some of them. There is some pod that is still error:` Error: failed...
Architecture is x86_64, using rhel 8.7 (ootpa) Running `microk8s ctr run registry.k8s.io/pause:3.9 foo` returns shutting down, got signal: Interrupt. This cluster previously encounter multiple error and fixed by other people....
Everything works fine now after some possible fix that might be fixing this: 1. Disabling kaspersky endpoint agent 2. Upgrading container image (image is fine in 1.25, but probably there's...
The error is back with similar message: > Error: failed to create containerd task: failed to create shim task, OCI runtime create failed: ruinc create failed: unable to start container...
Any solution to this?
I got issues with pnpm v10.4.1 and turborepo v2.4.2. In dockerfile, pnpm install returns fine. But when running pnpm build (requires prisma generate), it returned error sh: prisma: not found....