Developers hit rough edges using DevContainers across tools
Developers who work in DevContainers report gaps in their editor and terminal workflows: they may have to reopen projects manually, select the right workspace themselves, or give up their preferred terminal because it cannot use the container. Some resort to custom scripts and awkward command-line workarounds. The evidence is strongest around DevContainer launch and access; other container requests in the cluster are related but not all the same problem.
For developers who work in DevContainers. Mentioned from May 2019 to May 2026 on Bluesky, GitHub and Hacker News.
27 different people described this problem in 15 separate discussions.
- Indie fit
- 5.0/10
- Pain
- 5.6/10
- Frequency
- 10.0/10
- Willingness to pay
- 1.9/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
I've used Warp before and really enjoyed it, but had to stop because of this limitation. Most companies I've worked at use DevContainers to unify the developer experience across the team, making this a blocker for adoption
Warp is an absolutely amazing tool, but unfortunately remains unusable for real work without devcontainer support. Subscribing to this thread so I can immiedately switch to Warp if this is ever resolved
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 5 places to find your first customers
- 27 more quotes from people who have this problem
- Current workarounds, existing solutions and risks