Trying to access a #VSCode #DevContainer from another computer on your network?

Set “remote.localPortHost” to “allInterfaces” (thats an uppercase “i” in there). Ports exposed by your app running in the container will now be accessible by the host machine’s IP address.

Today I learned how to use #DevContainer in #VSCode for my #Python projects.
Interesting concept, will most probably replace my #venv for python

For those of you #emacs users who are looking for a way to work with a #devcontainer checkout https://github.com/johannes-mueller/devcontainer-mode

I started its development like two months ago and its working quite well for me. I would like to get some input like missing user stories or general issues that are worth addressing.

Long time without writing on my blog, let's talk about Dev Containers this time.

DevContainers: Migrating my entire Rust setup - https://www.edu4rdshl.dev/posts/devcontainers-migrating-my-entire-rust-setup/

I've been struggling with getting a larger .NET Project to open in a DevContainer. Specifically, the language server kept dying and I was always too busy to figure out why.

It was running out of memory!

Docker on my dev machine had a max memory allocation of 8GB and limited swap. Cranking that up and everything is lovely!

Why didn't I catch this earlier?!

Just past month I consulted a company, and I said they shouldn't renew #JetBrains, and fully transition to #VSCode and Coder.

Past week they did. They took three days to replicate their development environment, and a week to move from their muscular memory.

Nothing against JetBrains, but their products feel like 2005 crap on 2015 interfaces and 2025 promises.

My beef with #PHPStorm is not unfounded.

I still believe it wasn't made with Containers in mind and the codebase is "patched" to work with containers.

I've seen two workplaces pivoting to containers and VSCode. Their developers just abandoned #JetBrains for this same reason. Container workflows suck and it's full of inconveniences.

Damn, #Fleet doesn't support remote #PHP interpreter.

Guess I'll have to juggle around #PHPStorm while they get their shit together around DevContainers.

Meanwhile, I'm hoping #Zed catches up. As soon it brings the important bits from PHPStorm, I'm moving on.

Not renewing my #PHPStorm subscription. I'll do once #DevContainer support is as good as #VSCode.

"Hey, try DevPod instead, I've never had a problem using it with PHPStorm"

It did fucking work. How the hell.

Is this a fucking joke, #JetBrains?

That's it, moving on from #PHPStorm and their half-ass implementation of #DevContainer, it's fucking shit. JAVA was a mistake.

Let's test Zed. Worst case scenario, VSCode.

Am I using #Github #Codespaces wrong?

I thought the point of creating a devcontainer.json file to specify extra bits have built when you set up a machine, and they were honoured on the creation of codespaces.

Given that #Gitpod seems to be adopting #devcontainer now, I figured I'd try Codespaces. A basic thing seems to be harder than I thought.

If you have direct experience building Codespaces, would you share a pointer on how to fix this seemingly basic thing?

https://gist.github.com/mrchrisadams/9ee981ffdcc1cef38431f51a76886098

I stumbled upon #Coder, which is a #DevContainer platform you can use in your own computer (much like #DevPod).

I'm going to give it a spin to see if I can connect remotely to a DevContainer on another computer. It "should" work, since it's made for this type of scenarios, unlike DevPod which focuses on local.

https://coder.com/

Dev Containerを使ったら超効率よく開発環境ができた話【Ruby on Rails】
https://qiita.com/maabow/items/bbd2109bd3dcaa176a79?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items

If you, just like me, wanted to try Dev Containers, but couldn't, because there was no support in VS Codium, I made an extension. I made it primarily for my own needs but I invite you to try it and contribute too.

The way it works is extremely simple. It builds containers with DevPod (https://github.com/loft-sh/devpod) and connects to them using Open SSH extension (https://github.com/jeanp413/open-remote-ssh). That's it.

You can find it at:
- https://github.com/3timeslazy/vscodium-devpodcontainers
- https://open-vsx.org/extension/3timeslazy/vscodium-devpodcontainers

While making this extension, I also wrote some of my thoughts about dev containers tooling. You can read them here: https://techhub.social/@3timeslazy/113022591492167578

I would also like to mention @sitnik_ru 's thread on this topic: https://mastodon.social/@sitnik_ru/112478911770136745. I knew about devcontainers before, but this thread nudged me to try them again and eventually create my extension. As a thank you, I made a couple of contributions to the slowreader (https://github.com/hplush/slowreader).

I don't know if my project to make a DevContainer for #Laravel is "acceptable".

It works by shoving a Valkey, a SQL Database, PHP and some other things into a single container.

Should I have used a Docker Compose instead of a single container?

https://blog.saeloun.com/2024/07/31/rails-7-2-adds-support-for-devcontainer/

Alright, I am intrigued. One thing I noticed in the example is that the mounts were specific to the developer, and I wonder about that portability. But hey, I need to give this a try and see what I can see.

Okay so I love the idea behind project-specific dev containers, but I'm constantly wishing to reply less on VS Code. DevPod is great for that, and then I can run nvim inside a remote container.

Is anyone aware of a CLI tool that will prompt you through the existing dev container templates and features, kind of like VS Code does? I'd also love the ability to add custom repos.

I think Laravel has a mess of development environments. Sail? Herd? Valet? Serve?

For fuck sake, stick to one that works anywhere without installing a fucking forest and call it a day. Bonus points for a GUI.

To me, the obvious choice is make something based on DevContainers.

WSL2 users can fuck off outside VSCode.