-
Notifications
You must be signed in to change notification settings - Fork 379
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
MeTube Webpage not working on Portainer #337
Comments
it looks works fine. use http://yourPortainerIP:9995/
it looks like some issue of network. please go to networks in portainer and check which network is using for metube |
I'm concerned that this issue may be affected by the notoriously bad DNS compatibility problem present in all musl-based distros and Docker images, including Metube. The DNS compatibility is so problematic that it leads to issues from time to time. For example alpinelinux/docker-alpine#155 and kubernetes/kubernetes#112135. The bottom line is, if musl doesn't cooperate well with your DNS server's behavior, it can result in DNS resolution errors. One common cause, even in simple setups, is that musl queries both A and AAAA records at the same time, and the failure of the AAAA query would even fail the A query. If the DNS server rejects the AAAA resolution because it doesn't support AAAA records and returns a Similar problems can also occur when there are multiple upstream DNS servers, and the address is not resolvable in all of them. This issue is even documented by Alpine Linux. Such behavior is caused by the flawed design of musl, and there is little you can do about it. Alpine Linux recommends setting up a local DNS caching server using Dnsmasq and using that as the DNS for your musl-based systems if you are experiencing DNS compatibility issues. A faster way to check if it is indeed the DNS issue is to manually set the DNS to 8.8.8.8 for the container. As far as I know, Google's DNS works fine with musl. |
I've been using alpine for a long time and never had this problem. |
Thanks. It was mistake of my own, I had setup as a stack so portainer created a separate host which didn't have access. I deleted and created a simple container and it worked. |
Running the application on Portainer and the container is up without any error however the web page is not coming up.
Docker Compose
Log
I ran the ping command from within the container and below is the error
The text was updated successfully, but these errors were encountered: