Setting up #devcontainer for my #LeetCode playground repo, help me Cthulhu

To the developers using Mac OS X with Docker. Is there a demand for a chargeable device that allows you to run Docker without killing your battery or depleting your hard-drive? Something like a "physical" Docker machine that you can switch on and off for development purposes.

Note that this USB accelerator/accessory would pull arm64 images even when your workstation is based on an amd64 processor.

#containers #docker #podman #devcontainer #linux #macos #battery #storage #hardware #accelerator

A couple of docker rebuilds later (Acquiring CodeLLDB platform package is soo fun to wait for), it turned out that

"containerEnv": {

"CARGO_NET_GIT_FETCH_WITH_CLI": "true"
},
"mounts": [
"source=${env:HOME}/.ssh,target=/home/devuser/.ssh,type=bind",

in devcontainer.json do the job, so all is clear for a proper build.
#rustlang #devcontainer #ssh

Wow, wieso entdecke ich #devcontainer erst jetzt? Das ist ja mal n herbes Upgrade für die Dev-Experience :awesome: Ich installiere mir nie wieder nativ irgendwas.

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.

Trying to use a #DevContainer to work on an existing open-source project that uses #CMake . The devcontainer works great for the build, I can set up the various dependencies to only be installed in the container, keeping the host nice and clean.
It's not trivial to _run_ the application after it's built however. It's a GUI app, so running from inside the container doesn't seem to work (cannot connect to display). Running outside doesn't due to the missing shared libs.
(1/N)

2025年版Elixir×VSCode×コンテナで始めるお手軽環境構築
https://qiita.com/misohagi/items/d8e3e80f6f22c042a33c?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items

#qiita #Elixir #Docker #Phoenix #VSCode #devcontainer

企業でCline導入のために開発環境をコンテナ化し，セキュリティ対策を考える #devcontainer
https://qiita.com/sigma_devsecops/items/623eefcb95edc26a965a?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items

#qiita #devcontainer #Codespaces #生成AI #cline #コンテナセキュリティ

It would be hard for me to overstate how much I love pgweb (https://github.com/sosedoff/pgweb). It's a single executable web-based Postgres client that’s feature rich, simple, fast and super lightweight. It pairs nicely with my DevContainer for poking around the DB in the container. #postgres #development #devcontainer

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/

#rust #linux #development #devcontainer #programming

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?!

#development #docker #devcontainer #dotnet

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.

#IDE #Programming #Technology #Containers #DevContainer #RemoteDevelopment #JavaScript #JS #PHP #Rust #Go #C #Node #nuxt

Giving this #Emacs (/ #DoomEmacs ) #devcontainer config a go, so far it's working surprisingly well. I hope I can completely ditch #VSCode with it, at least for most tasks.
Edit: well, there is this bug: https://github.com/doomemacs/doomemacs/issues/6079
https://github.com/nohzafk/emacs-devcontainer

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.

#Programming #SoftwareDevelopment #ContainerDevelopment #DevContainer #Container #OCI #Docker #Podman #PHPStorm #WebStorm #VSCode #WebDevelopment #WebDev

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.

#JetBrains #Development #SoftwareDevelopment #AppDavelopment #WebDev #WebDevelopment #Containers #Container #Docker #OCI #DevContainer #DevContainers #IDE #Programming

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

#Programming #PHP #JetBrains #JAVA #Docker #Container #Podman #OCI #Containers #Technology #IDE #AppDevelopment #WebDevelopment #WebDev #Development #SoftwareDevelopment

A day later, with my head clear, I noted a discrete but clear statement in #vscode #devcontainers documentation (https://code.visualstudio.com/remote/advancedcontainers/connect-multiple-containers):

If you want to extend your Docker Compose file for development, you should use a single docker-compose.yml that extends both services (as needed) and is referenced in both devcontainer.json files.

So, __single__ docker-compose.yml that extends __both__ services.
And I had an extending docker-compose.yml __per__ service.
Of course that wouldn't work. Once you build one #devcontainer (and use one of the extending docker-compose.yml) the other #devcontainer will have to be invalidated.
Now, with a __single__ extending docker-compose.yml for all the services, everything is hunky-dory, it seems I'll be developing #rust in #devcontainers just fine! 😎 😜

All the "standard" (#postgres and #rabbitmq ) #docker nodes get up without a problem.
The first #devcontainer also gets up (ok, tuning all the appropriate files might get a bit tricky)
But, building a second #devcontainer always fails, at least with #vscode 1.95.3.
It doesn't matter which #devcontainer I build first, the next one cannot be built. I'll skip copy-pasting the error here

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

It did fucking work. How the hell.

#DevPod #DevContainer #DevContainers #OCI #Containers #Docker #Podman #FOSS #OSS #OpenSource #Programming #Software #SoftwareDevelopment #AppDevelopment #WebDevelopment #WebDev

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.

#Programming #AppDevelopment #Software #SoftwareDevelopment #Development #WebDevelopment #WebDev #DevContainers #Docker #Containers #Linux #OCI #FOSS #OSS