I have a dev container for VS Code, it works perfectly but when I connect to VS Code it asks for a password
Dockerfile:
I have a dev container for VS Code, it works perfectly but when I connect to VS Code it asks for a password
Dockerfile:
VSCode devcontainer terminal opens http://127.0.0.1:8080 as http://0.0.0.0:8080
I am working within VSCode. I am using its devcontainer feature and a bash terminal.
Can I force vscode to open a port inside a devcontainer?
I’m a fan and advocate of using Visual Studio Code devcontainers however I’ve hit a snag when using them.
Our organisation uses a service called Snowflake (its a cloud-based analytical DB, not that that’s important). They have a command-line tool called snowsql
that is used to interact with the service and in order to use snowsql
one must first authenticate. The easiest way to do that is to use browser authentication whereby a browser is opened to allow me to enter my credentials and then a token is passed back to snowsql
.
VSCode Dev Containers does not show “Attach Visual Studio Code” in right-click menu for a pod
I’m trying to follow the suggestions from the “Attach to a running container” article by Visual Studio Code and the image there shows an “Attach Visual Studio Code” in the right click menu for a pod.
Why is Visual Studio Code not auto forwarding ports?
I am using a service called Snowflake (a hosted analytic database service) and the CLI tools to interact with the service launch a browser window in which I enter my authentication details. The return URL of that authentication request goes to localhost:<port>
where port is different each time.
Caching requirements on dev containers for possible rebuilds
I am working with a project that has several containers being managed by Docker Compose. I realized that was easier to make VS Code editor connect to these containers to make features like auto-complete to work properly.