-
-
Notifications
You must be signed in to change notification settings - Fork 406
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: Docker container is unhealthy and won't spin up - Host is unreachable (fd=3,code=113) #2705
Comments
@qdm12 is more or less the only maintainer of this project and works on it in his free time.
|
I had this issue as well, with a bit of searching I came across this post that fixed it for me by running |
I have this issue also, removing the service, rebooting and then re-adding didn't fix the issue, nothing has changed except the system update. Did you manage to fix this? |
Got the same issue, no solution worked so far. What did work was restoring a backup where I didn't have the latest updates installed. I noticed the output of "docker ps" containing IPv6 syntax ([::] instead of 0.0.0.0) after the update, maybe that could be related to that? |
It may have something to do to this if you're using Tailscale also: moby/moby#49498 |
@maxexcloo I tried a few more things as well as what @neverwantit suggested, but it still didn't work. I ended up mounting a boot volume backup I made in December and now everything is working as before. If the dev picks up this thread and thinks it's container related, I'm happy to remount the problematic image to do some troubleshooting, but my guess is it might be an Oracle-related issue. |
Is this urgent?
No
Host OS
Canonical-Ubuntu-22.04
CPU arch
aarch64
VPN service provider
ProtonVPN
What are you using to run the container
docker-compose
What is the version of Gluetun
Running version latest built on 2025-01-22T08:30:14.628Z (commit 13532c8)
What's the problem 🤔
I have a VM on Oracle Cloud. Since 2 days, I can't spin up the container because it is unhealthy/fails the health check. Nothing about the compose or configuration has changed. I did run a list of system updates/upgrades a few days ago, which I think aligns with when I started noticing the issue, but it could just be coincidental.
What I've tried
Share your logs (at least 10 lines)
Share your configuration
The text was updated successfully, but these errors were encountered: