Which part of the documentation is correct re launching dev containers from remote machines?
This is my setup:
- one local machine running Windows 11 and an un-update-able CLion 2025.2 RC Build #JBC-252.23892.298
- one remote machine running Ubuntu 22 and a snap CLion 2026.1.2 Build #CL-261.24374.148
- one dev container on the remote machine running RHEL 9.5
Currently to use the dev container, I connect to 2 from 1 via RDP and start CLion there.
I would like to (like VSCode can do) use the dev container with 1 as the frontend.
Here is what the documentation claims:
So far it did not work. But perhaps that is only the fault of my outdated Windows-CLion-Version and if I pestered the administrators enough to get me a newer one, then it would work?
Which part of the documentation is correct? What minimal version of CLion do I need?
请先登录再写评论。
Hello, simon.beyer.external.
The scenarios mentioned in the documentation are different; we don't support running a dev container from the already established Remote Development connection as VSCode usually does. To run a dev container on the remote server, the process of dev container build should be started from the local IDE or Gateway, not from the Remote Development functionality.
If you have an SSH connection to your remote server, you can build and use the dev container on it; in this case, the client will be started on your local machine and the backend in the container on the remote server.
The IDE version you mentioned that is installed for you locally is a JetBrains Client, not the full CLion IDE itself (either CLion itself or Gateway is necessary to start the dev container on the remote server).
2025.2 should support the remote server scenario for dev containers; however, we fixed some bugs for the remote scenario since then, so I'd recommend using the latest available version.