Up until now we’d been making do with docker-compose and JetBrains’s remote SSH dev; this should be significantly better.
Both .devcontainers and .devfile managed to create more effort than they took away. Some key points:
- long lived containers
- abstracting away the fact that you run stuff inside containers in the IDE and abstracting away the container life cycle
- cryptic error states and error messages, especially when setting up new projects from scratch. This often boiled down to bad plugins (even Microsoft's own VSCode plugins wet the bed often)
- only superficial support for podman
- bad support for arm based HW (and arch translation issues, like a tool requesting arm containers but the host running docker is x64)
At this point I consult teams to try out a plain compose.yml as a CDE and skip the "enterprise" stuff.
For devcontainers even the reference implementation CLI is significantly incomplete.
Looks pretty useable to me...
[0]: https://github.com/devcontainers/cli?tab=readme-ov-file#cont...
Does that require a static ip on remote?
I have skimmed the Jetbrain FAQ [1] and it says "no relay servers are involved"
[1] https://www.jetbrains.com/help/idea/faq-about-remote-develop...
You can use something like the following in your ~/.ssh/config:
Host devhost
ProxyCommand aws --profile DevProfile ssm start-session --target i-0123456789abcdef0 --document-name AWS-StartSSHSession --parameters "portNumber=22"