[tailscale] Stuck in deploying after updating to 1.0.43
maxexcloo opened this issue · 7 comments
My containers no longer run after the update - tested a rollback to the previous version 1.0.42 and all was working again.
Logs show this:
2024-08-01 16:11:56.378142+10:00boot: 2024/08/01 06:11:56 error checking get permission on secret tailscale-tailscale-secret: Post "https://kubernetes.default.svc/apis/authorization.k8s.io/v1/selfsubjectaccessreviews": dial tcp: lookup kubernetes.default.svc on 100.100.100.100:53: read udp 192.168.0.3:45884->100.100.100.100:53: i/o timeout
2024-08-01 16:12:16.389336+10:00boot: 2024/08/01 06:12:16 error checking update permission on secret tailscale-tailscale-secret: Post "https://kubernetes.default.svc/apis/authorization.k8s.io/v1/selfsubjectaccessreviews": dial tcp: lookup kubernetes.default.svc on 100.100.100.100:53: read udp 192.168.0.3:36622->100.100.100.100:53: i/o timeout
Happy to give any more info needed :)
I faced the same issue with 1.0.43. But I manage to have it run after clicking on pause and click on start again for the container to restart. Maybe you can try this too?
Otherwise you may share your configuration on Tailscale. As of now I am running Tailscale 1.0.43 without problem.
I'll give that a go, just don't want to lose my remote access!
I'll give that a go, just don't want to lose my remote access!
Hello, Did that work?
I couldn't reproduce it locally.
I completely uninstalled and reinstalled and had the same issue - very odd
New config with a new name, same issue:
2024-08-28 13:59:26.286844+10:00boot: 2024/08/28 03:59:26 error checking get permission on secret tailscale2-tailscale-secret: Post "https://kubernetes.default.svc/apis/authorization.k8s.io/v1/selfsubjectaccessreviews": dial tcp: lookup kubernetes.default.svc on 100.100.100.100:53: read udp 192.168.0.3:34019->100.100.100.100:53: i/o timeout
2024-08-28 13:59:46.300039+10:00boot: 2024/08/28 03:59:46 error checking update permission on secret tailscale2-tailscale-secret: Post "https://kubernetes.default.svc/apis/authorization.k8s.io/v1/selfsubjectaccessreviews": dial tcp: lookup kubernetes.default.svc on 100.100.100.100:53: read udp 192.168.0.3:41605->100.100.100.100:53: i/o timeout
It starts up, adds itself to the tailscale admin and then restarts and won't start after that...
Just saw the news about docker, I guess it’ll work with that ☀️