Looks like it's officially possible to self-host vscode server and access it through vscode.dev (also see this GitHub issue).
For reaching it through custom URL consider using Gitpod's OpenVSCode Server fork of vscode.
If you just want to share your configuration between machines, it's probably simplest to just use settings sync, which is available in default installation.
Answer from Matija Sirk on Stack OverflowGoal
Having multiple containers with different vscode instances.
Example: I want one container with a vscode with the necessary extensions (and dependecies) to do web development, other container to do back-end development, and other to do data-science development. This will avoid having tons of extensions in the same VScode instance, wich sometimes, causes conflicts.
As far as i know, this can be done accessing via browser pointing to a port of the container running VScode right? Can i access without the need of browser? This is because i use a lot keyshortcuts and i'm afraid they don't work if use VScode via browser. Also, is the performance a concern or will it run smoothly?
Some references
site A
site B
If you have other references other than the ones i provided, please share.
visual studio code - How to run VSCode in a docker container - Stack Overflow
python - How to use VSCode with the existing docker container - Stack Overflow
visual studio code - open a file in docker container with vscode - Stack Overflow
Installing VS Code in a Docker container
Videos
I use such an environment to develop python app inside a container.
image_create.sh # script to create image to use it local and on the server
image_dockerfile # dockerfile with script how to create an image
container_create.sh # create named container from image
container_restart.sh # restart existing container
container_stop.sh # stop existing container
Examples:
image_dockerfile :
FROM python:3.9.15-slim-bullseye
USER root
RUN pip3 install requests telethon
RUN apt-get update
RUN apt-get --assume-yes install git
image_create.sh :
docker rmi python_find_a_job:lts
docker build . -f python_find_a_job -t python_find_a_job:lts
container_create.sh :
docker rm -f python_find_a_job
docker run -t -d --name python_find_a_job -i python_find_a_job:lts
docker ps -aq
container_restart.sh :
docker container restart python_find_a_job
docker ps -aq
container_stop.sh :
docker stop python_find_a_job
docker ps -aq
For VSCcode:
a) Prepare files (see above).
b) Run:
image_create.sh
container_create.sh
c) Open project folder in VSCode
d) Click on left bottom green / Attach to running container / select container name (python_find_a_job).
e) Clone repository.
f) Install extension 'Python'.
Now you can run and debug inside the container.
After work:
git push
container_stop.sh
Before work:
container_restart.sh
git pull
Visual Studio Code, and Docker Desktop each offer a feature called "Dev Containers" (VSCode) or "Dev Environments" (DD), or CodeSpaces (GitHub)
In this approach, a Docker container is created by scanning the source, and generating a container that contains the development toolchain. Visual Studio then attaches to the container, and allows you to develop even though you do not have node/python3/dotnet/etc. installed on your development PC.
The xhr error indicates something went wrong downloading a scanning image or something else is strange about your project.
There is an optional Dockerfile that can be created if scanning fails to find an image, that is normally kept in a .devcontainers / .devenvironments folder depending on which of Docker / VSCode / GitHub / other you are using.
Your project might also have one (or more) Dockerfile's that are used to package the running app up as a docker image, so don't be confused if you end up with 2. Thats not a problem and is expected really.
With the May, 2nd 2019 announcement of "Remote Development with VS Code", you actually can use The Remote - Containers extension :
The Remote - Containers extension lets you use a Docker container as a full-featured development environment.
Containers make a great development environment because you can:
- Develop with a consistent and easily reproducible toolchain and on the same operating system you are deploying to.
- Quickly swap between different, isolated development environments and safely make updates without worrying about impacting your local machine.
- Make it easy for new team members / contributors to get up and running in a consistent development environment.
Docker extension for VS Code (ms-azuretools.vscode-docker) allows you to right-click on any running container in the list, then choose 'Attach Visual Studio Code' - and you will be able to open any folder inside Docker container in a new VS Code window. I presume you must have The Remote - Containers extensions installed as well.
Hello,
I have been using VS Code for some years and recently started using Docker, but I am not an expert in IT infrastructure so I would like to know if it is possible to literally have VS Code and the elements required to use notebooks (Ipykernel, Python, etc) installed in a container, so that I can directly use it anywhere.
The reason for this approach is that I am working with some data hosted in an offline server, and the only way to work in there is through the packages and modules you install in a container. I can already use Jupyter notebook as it seems to be quite simple to get - just including python, its packages, and Jupyter notebook in the container.
However, I really am not a fan of Jupyter and I would love to set up a way to have VS Code run on that server. I would greatly appreciate any tips that anyone could give :)
Thanks a lot!
Best regards,
Red muffin