[whinvik]

Yes, it feels very similar to Devcontainers.

But having tried Devcontainers a lot, it feels like its probably a complex specification since outside of VSCode every implementation has issues.

The CLI on Mac has weird user permission issues. Cursor's implementation is very flaky. Zed doesn't implement it yet.

So maybe there's space for more solutions in the same space but Devcontainers are very feature rich. And not to mention they have a huge user base via VSCode.

[NitpickLawyer]

The killer combo for us is remote+devcontainers. We use this for GPU access, so you can run a project on one or more GPUs that are on a remote server. You can spin up LLM stuff from a mac air and get the best of both worlds.

[runelk]

Nice! Do you have any tips or recommendations for a decent setup?

[phrotoma]

This has been my experience. I don't use VSCode and every time I've attempted to play with devcontainers I've just given up and gone back to a docker compose file. I love that they tried to extract the feature out into a stand alone thing, but the juice doesn't seem to be worth the squeeze yet.

[immutology]

Devcontainers work nicely with docker compose. It's the only way I use it... Really nice to have it all run containers.

https://code.visualstudio.com/docs/devcontainers/create-dev-...

[phrotoma]

Cool! I haven't seen this feature. Does it add some nice features beyond what a compose file could offer?