xtex
@slimus I just: 1. install kubectl kubelet kubeadm 2. try to install with kubeadm, failed 3. delete kube config files manually(.kube /etc/kubernetes) 4. apt remove kubectl kubelet kubeadm 5. install...
> That makes sense. With no config, we use the default server URL and you see it in your logs. > @derailed should we use the default server or fail...
stale and I do not use k8s any more
Looking forward to it!
cc @Clexus
The same error.
one container could not be started after re-creation ``` time="2023-05-18T18:10:24Z" level=info msg="Found new docker.io/binwiederhier/ntfy:latest image (2434c49f7c33)" time="2023-05-18T18:10:26Z" level=info msg="Stopping /ntfy (09b65f2ca3c5) with SIGTERM" time="2023-05-18T18:10:27Z" level=info msg="Creating /ntfy" time="2023-05-18T18:10:27Z" level=error msg="Error...
lgtm, I wouldn't recommend anyone to use such a slow backend without a special reason however it is pretty useful for some special cases.
The same error on eowiki's latest dump. I solved by merging #313