CLion Air Gapped remote using Docker
已回答
https://www.jetbrains.com/help/clion/fully-offline-mode.html
Has anybody actually got an air gapped system using CLion to work using docker to run
a container that contains the downloaded files? And then connect to a different container for development?
I don't mind if the webserver is in the development container.
The problem I am trying to solve is that I am often in location where my laptop has poor internet,
and the loading of the backend will take 2 hours, and then fail.
请先登录再写评论。
Hi marc pawlowsky!
Could you please describe your setup and scenario in more detail? Where should the building/running/debugging processes take place? Inside a Docker container? If so, where is this container, on the local machine or remote machine? Where is the project located?
Are you currently using the Dev Container scenario of Remote Development? If so, could you please clarify why you chose it rather than the Docker toolchain?
Process used is in https://github.com/marcpawl/esp32_sensors.git in the branch jetbrains_remote. On a system with docker and CLion installed, execute
python clion_remote_setup.py
It will create the docker containers, and tell you when to disconnect from the internet, and then run CLion and reopen the project in the devcontainer.
marcpawl@sam:~/github/esp32_sensors$ clion --version
CLion 2026.2.3
Build #CL-262.10968.117
marcpawl@sam:~/github/esp32_sensors$ lsb_release -a
No LSB modules are available.
Distributor ID: Linuxmint
Description: Linux Mint 22.3
Release: 22.3
Codename: zena
marcpawl@sam:~/github/esp32_sensors$ uname -a
Linux sam 7.0.0-34-generic #34~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 4 15:38:29 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
marc pawlowsky, if I understand correctly, you create a
jetbrains-backendscontainer to download CLion builds and then use it as a web server for downloading CLion builds when creating a Dev Container session with youresp32-sensors-devdevelopment container.Instead of creating/using the
jetbrains-backendscontainer, you can manually download the IDE backend on the local machine and specify its path when building the dev container. The process is described in SUPPORT-A-258.