-
-
Notifications
You must be signed in to change notification settings - Fork 385
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: latest
tag in docker image points to unstable version
#2387
Comments
@qdm12 is more or less the only maintainer of this project and works on it in his free time.
|
latest
tag in docker image points to unstable version
I'm guessing this was my problem as well. Gluetun wasn't able to find any servers using the |
Using |
See https://github.com/qdm12/gluetun-wiki/blob/main/setup/docker-image-tags.md latest points to the master branch. There has been extensive debate why this is as such (summary: have more people testing the 'beta' to have more stable releases). Since the original poster did not actually include a 'bug' description - except that latest should be v3 I think 🤔....
What servers? Can you please provide details?? @marcosvrs same, I need details, what issue are you having |
It seems this is more of a misexpectation from my part. I use Watchtower, and noticed that the latest tag is pointing to an unstable release, since it's getting updated every day. This caused some issues with other Docker images that rely on Gluetun’s network and require a stable internet connection. (I know, doesn't make sense to update containers automatically if I require them to be stable, but this is something I just realised while investigating it :D) Wouldn’t it be clearer to highlight in the README file that it points to the master branch, which might be unstable? Thanks again for your efforts on this project! |
Hey, sorry for not providing more details earlier. Looks like the container is failing the healthcheck because it cannot find any servers. Here's my compose:
This is the error that shows up in the logs and triggers the healthcheck failing: This configuration, as shown by the error, does not work when using the |
@marcosvrs See #556 (comment) this has already been discussed in the past 😉 And the solution brought is a @forkentiney I just tried with the current latest image and it works fine, it finds me server |
Closed issues are NOT monitored, so commenting here is likely to be not seen. This is an automated comment setup because @qdm12 is the sole maintainer of this project |
Yesterday I also had the same issue of gluetun not finding any servers on protonvpn on latest; I found the cluprit to be VPN_PORT_FORWARDING, disabling it would find the servers again. |
@qdm12 Looks like that did it. Thanks. |
Is this urgent?
None
Host OS
No response
CPU arch
None
VPN service provider
NordVPN
What are you using to run the container
docker run
What is the version of Gluetun
v3.38.0
What's the problem 🤔
The
latest
tag in docker image points to unstable version:It should point to the latest stable one, or? (v3.38.0)
Share your logs (at least 10 lines)
Share your configuration
The text was updated successfully, but these errors were encountered: