-
Notifications
You must be signed in to change notification settings - Fork 516
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
Open in Browser using 0.0.0.0 not the remote context #4214
Comments
IIRC we use the results from container inspect to determine the IP to connect to. Can you do |
Sure here is the output of the docker inspect on the container.
|
What address do you get if you do |
nslookup dind Non-authoritative answer: |
It may not be possible to make the Open in Browser command open the right URL, since neither the hostname ( |
Thank you for looking into it. I was hoping for some way to just pass the info into it maybe through an env variable or maybe add a label to the container itself that would show up. |
Bottom Line Up Front (BLUF): Is there a way to configure the ‘Open in Browser’ option to direct to a specific IP address or hostname, instead of defaulting to 0.0.0.0?
I have a setup where a Visual Studio Code (VSCode) server is running within my Docker swarm, alongside a Docker-in-Docker (dind) container. Both are interconnected via a Docker network. I’ve configured the Docker context within the VSCode server, enabling me to execute Docker commands and spawn new containers within the dind container from the VSCode server without any issues.
Additionally, I’ve installed the Docker extension in my VSCode server environment. When I initiate a container and select the ‘Open in Browser’ option from the Docker extension for VSCode, it launches a new browser window. However, it returns an error: “connect ECONNREFUSED 0.0.0.0:8080”.
My question is: How can I configure the system so that when I select ‘Open in Browser’ for a container, it establishes a connection to the dind container over the Docker network, rather than attempting to connect using 0.0.0.0:8080?
For reference, I can successfully curl the dind container from the terminal inside VSCode using the command: curl http://dind:8080.
The text was updated successfully, but these errors were encountered: