home.social

#devcontainers — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #devcontainers, aggregated by home.social.

fetched live
  1. Posted about my dev container setup that aims to give me a bit more peace of mind when working on my hobby projects:

    blog.nytsoi.net/2026/08/08/dev

    If you reply to this post publicly, that reply will be shown in the blog.

    #DevContainers

  2. Posted about my dev container setup that aims to give me a bit more peace of mind when working on my hobby projects:

    blog.nytsoi.net/2026/08/08/dev

    If you reply to this post publicly, that reply will be shown in the blog.

    #DevContainers

  3. How do you keep dev environments aligned across laptop, cloud & CI?

    At #PSConfEU, @[email protected] shows how #DevContainers:
    ✅ Remove setup issues
    ✅ Standardise environments
    ✅ Speed up onboarding

    👉 youtu.be/jsp1mZVhDzQ?si=WYP...

    #PowerShell #automation #IT #DevOps #Conference

    - YouTube

  4. How do you keep dev environments aligned across laptop, cloud & CI?

    At #PSConfEU, @[email protected] shows how #DevContainers:
    ✅ Remove setup issues
    ✅ Standardise environments
    ✅ Speed up onboarding

    👉 youtu.be/jsp1mZVhDzQ?si=WYP...

    #PowerShell #automation #IT #DevOps #Conference

    - YouTube

  5. I need to write a blog post about this I guess, but due to the prevalence of supply chain attacks nowadays, I've slowly moved all of my personal projects to devcontainers. Meaning the source is replicated from the host and I use git on the host, but any installing/compiling is done in a Docker container on a non-root user. It has worked mostly transparently through VSCode and adds a layer between me and a possible attacker. I think it's spiffy.

    Example: git.ahlcode.fi/nicd/zones

    #DevContainers

  6. I need to write a blog post about this I guess, but due to the prevalence of supply chain attacks nowadays, I've slowly moved all of my personal projects to devcontainers. Meaning the source is replicated from the host and I use git on the host, but any installing/compiling is done in a Docker container on a non-root user. It has worked mostly transparently through VSCode and adds a layer between me and a possible attacker. I think it's spiffy.

    Example: git.ahlcode.fi/nicd/zones

    #DevContainers

  7. All I want for my birthday is to rebuild #devcontainers in #ZedEditor. You have 2 months or so. Thanks in advance.

  8. the same script has been running fine for days on my 2015 dell laptop so there's definitely something funky going on on the macbook.

    afaict i have not messed with the networking too significantly apart from installing a vpn.

    there was also a memory leak with the s3 sdk that just didn't happen on linux.

    i guess this was finally the push to reinstall #MacOS from scratch 😬

    who knows what supply chain malware i've accumulated over the years from the times i was smart enough not to use #DevContainers [1].

    [1]: containers.dev/

  9. do #devcontainers exist mainly because for anything other than .net, windows is an awful development environment? Or is there more to them?

  10. do #devcontainers exist mainly because for anything other than .net, windows is an awful development environment? Or is there more to them?

  11. Не настраивайте локальное окружение вручную. Devcontainers — уже пора! Часть вторая

    Привет, Хабр! На связи — любопытный DevOps Владимир Лила, и это вторая часть материала о девконтейнерах по мотивам моего доклада для

    habr.com/ru/companies/oleg-bun

    #devcontainers #devops #devopsconf #управление_конфигурацией #Онбординг #Безопасность_инфраструктуры #виртуализация

  12. Не настраивайте локальное окружение вручную. Devcontainers — уже пора! Часть первая

    Онбординг — один из важных аспектов, требующих особого внимания при масштабировании компании. А теперь представьте, что у вас есть универсальный инструмент, который помогает закрывать целый класс задач команды разработки: настраивает локальное окружение проекта одной кнопкой, унифицирует окружение для всех разработчиков на разных ОС, обеспечивает безопасность инфраструктуры, упрощает CI и многое другое. Всё это — девконтейнеры! Да, мы начинаем программировать прямо в контейнере. И всё это бесплатно и без необходимости развёртывания новых сущностей в вашей организации. О такой кнопке «сделать хорошо» мы и поговорим в этой статье по мотивам моего доклада для

    habr.com/ru/companies/oleg-bun

    #devcontainers #devops #devopsconf #Управление_конфигурацией #Онбординг #Безопасность_инфраструктуры #виртуализация

  13. Coding at the Speed of Thought: The New Era of Symfony Docker

    If we want to discuss Developer Experience (DX) in 2026, we have to talk about instantaneous feedback and coding agents. At SymfonyLive Paris 2026, I presented "Coding at the Speed of Thought: Symfony DX in 2026", where I detailed the bleeding-edge features we have brought to the PHP and Symfony ecosystems. To make this vision a reality, I have recently made dramatic improvements to the Symfony Docker project. While it remains the easiest way to spin up a Docker-based FrankenPHP skeleton for […]

    dunglas.dev/2026/03/coding-at-

  14. Coding at the Speed of Thought: The New Era of Symfony Docker

    If we want to discuss Developer Experience (DX) in 2026, we have to talk about instantaneous feedback and coding agents. At SymfonyLive Paris 2026, I presented "Coding at the Speed of Thought: Symfony DX in 2026", where I detailed the bleeding-edge features we have brought to the PHP and Symfony ecosystems. To make this vision a reality, I have recently made dramatic improvements to the Symfony Docker project. While it remains the easiest way to spin up a Docker-based FrankenPHP skeleton for […]

    dunglas.dev/2026/03/coding-at-

  15. Just a quick hack I noticed when spinning up with compose files outside VS Code fails (e.g., in or AntiGravity).
    Often, a simple docker compose up -d helps to spin up the services so the devcontainer only has to be attached.

  16. Just a quick hack I noticed when spinning up #devcontainers with compose files outside VS Code fails (e.g., in #zedEditor or AntiGravity).
    Often, a simple docker compose up -d helps to spin up the services so the devcontainer only has to be attached.

  17. Воспроизводимое изолированное окружение с Nix и DevContainers

    Как фулстек разработчику, мне доводилось работать с проектами на совершенно разных технологиях. Как правило, нужно было поправить небольшой баг или сделать небольшую фичу. Для задач такого разряда стек технологий обычно не имеет значения: отладка примерно одинаковая что на JavaScript, что на Haskell, Go или Python. Написать немного кода мне, в общем-то, никогда не было сложно на любом языке, с которым я работал. Но вот что всегда было настоящей проблемой — это запустить и протестировать проект. На это запросто уходили дни: найти нужные версии компиляторов/интерпретаторов, дебаггера, пакетного менеджера и всякого сопутствующего тулинга. Я устал от этого, и придумал, как больше никогда в жизни не устанавливать тулинг вручную.

    habr.com/ru/articles/1010282/

    #nix #devcontainers #docker #reproducibility #nixos #nixdarwin

  18. I’m rather smitten with the *idea* of dev containers and, to a degree, the reality delivers. Reproducible environments. Familiar primitives. Editors with decent adoption offer a good experience. Most engineers understand containers well enough to tolerate the rough edges.
    But I can’t shake the feeling there are better ways to reach the same goal.

    The usual answer is “Nix”, and that’s probably right. Yet the rise of Dev Containers feels less like a breakthrough and more like a side-effect of the container monoculture. They work because containers are everywhere, not because they’re especially well-suited to dev environments. If there’s a real successor, it likely abstracts Nix *away*, integrates cleanly with editors, and doesn’t require heavyweight plugins or full VM-scale artefacts to edit a file.

    What’s wrong with dev containers? They’re slow, expensive, and bloated relative to the problem they’re solving. I’m still invested, and I’ll keep using them. But it does feel like, as an industry, we’ve settled for the first thing that worked rather than the best thing we could build.

    #DevContainers #docker #vscode #zed #vim #jetbrains #python

  19. I’m rather smitten with the *idea* of dev containers and, to a degree, the reality delivers. Reproducible environments. Familiar primitives. Editors with decent adoption offer a good experience. Most engineers understand containers well enough to tolerate the rough edges.
    But I can’t shake the feeling there are better ways to reach the same goal.

    The usual answer is “Nix”, and that’s probably right. Yet the rise of Dev Containers feels less like a breakthrough and more like a side-effect of the container monoculture. They work because containers are everywhere, not because they’re especially well-suited to dev environments. If there’s a real successor, it likely abstracts Nix *away*, integrates cleanly with editors, and doesn’t require heavyweight plugins or full VM-scale artefacts to edit a file.

    What’s wrong with dev containers? They’re slow, expensive, and bloated relative to the problem they’re solving. I’m still invested, and I’ll keep using them. But it does feel like, as an industry, we’ve settled for the first thing that worked rather than the best thing we could build.

    #DevContainers #docker #vscode #zed #vim #jetbrains #python

  20. Is anyone using Development Containers
    (containers.dev/) for anything serious?

    I gave it a quick spin on a fairly simple Django + PostgreSQL projects, and all I see is flaky, half-assed implementations, stuff failing with cryptic stack traces, etc.

    Is it maybe because I am not using VSCode but PyCharm?

    Another thing a Megacorp can't afford to do properly?

    #Microsoft #DevContainers #DevelopmentContainers #SoftwareDevelopment

  21. Is anyone using Development Containers
    (containers.dev/) for anything serious?

    I gave it a quick spin on a fairly simple Django + PostgreSQL projects, and all I see is flaky, half-assed implementations, stuff failing with cryptic stack traces, etc.

    Is it maybe because I am not using VSCode but PyCharm?

    Another thing a Megacorp can't afford to do properly?

    #Microsoft #DevContainers #DevelopmentContainers #SoftwareDevelopment

  22. Running on an SSH remote feels like black magic.
    I can code without any feeling of latency, push code using my SSH public key, and launch GUIs that show on my client.

  23. Running #vscode #devcontainers on an SSH remote feels like black magic.
    I can code without any feeling of latency, push code using my SSH public key, and launch GUIs that show on my client.

  24. I've been slowly messing around with a #selfhosted instance of #Coder over the last two weeks or so. It seems very powerful and could help me resolve swapping between my #MacBook and #Macmini and not being able to pick back up where I left off.

    I need to learn more about how templates work, and how to build a custom one that meets my needs. I also want to learn a bit about #devcontainers.

    #code #selfhosting #Docker #Terraform #Kubernetes :docker: :kubernetes:

  25. I've been slowly messing around with a #selfhosted instance of #Coder over the last two weeks or so. It seems very powerful and could help me resolve swapping between my #MacBook and #Macmini and not being able to pick back up where I left off.

    I need to learn more about how templates work, and how to build a custom one that meets my needs. I also want to learn a bit about #devcontainers.

    #code #selfhosting #Docker #Terraform #Kubernetes :docker: :kubernetes:

  26. 🚀 We have now a Visual Studio Code Development Container for easy development!

    Install Dev Containers Plugin .

    Clone the WissKI Git Repo.

    Open the Dir with VSCode, Cursor or other compatible Codium Distro and click "Reopen with Dev Container".

    git.drupalcode.org/project/wis

    the marketplace.visualstudio.com/i

    #wisski #drupal #vscode #devcontainers

  27. a live without “Remote Development/DevContainers” sounds barbaric...

    #devcontainers #zed

  28. It's been a little over a year that I've been using #vanilla #emacs and customizing it almost from scratch.

    I liked it, I learned a few things here and there about its inner workings, but now is time to have a setup that gets me up to speed in a matter of seconds.

    Any suggestions ?

    I am particularly looking for a sane config that works out of the box for almost anything and is ergonomic (something like #ergoemacs) with stuff like:
    #devcontainers
    #lsp
    #snippets
    #editorconfig

  29. What are folks' thoughts on #devcontainers?

    I'm toying with them now because the main Python project I'm working on has a dependency that no longer builds correctly on macOS. (Python's xmlsec & native libxmlsec1)

  30. What are folks' thoughts on #devcontainers?

    I'm toying with them now because the main Python project I'm working on has a dependency that no longer builds correctly on macOS. (Python's xmlsec & native libxmlsec1)

  31. My hope for end-of-business-day Friday, May 8, 2025, is to have the start of a somewhat-user-friendly UX for #devcontainers in #Zed (including port forwarding). No guarantees. I like devcontainers, but I want to get #vscode out of my life, is the thing, is the thing.

  32. Ever been stuck with a messy dev setup? We've all been there!
    Manivannan Selvaraj shares how #DevContainers can save the day — making development faster, cleaner, and way less stressful at #FOSSASIASummit2025

    🔗 Click here youtu.be/5VmPYtY9D1s to watch on the #FOSSASIA YouTube channel.

  33. This week, I finally played with #devcontainers for the first time. I ran into a bit of issue accessing networking but that’s probably a me issue. So far I’m a fan!