#containers — Public Fediverse posts

From this week's ADMIN Update newsletter: @madkiss looks at how PipeCD for CI/CD works and what to expect if you're migrating from ArgoCD
https://www.admin-it.io/pipecd-for-ci-cd/?utm_source=mam
#PipeCD #ArgoCD #orchestrator #Kubernetes #Linux #containers #K8s

From this week's ADMIN Update newsletter: @madkiss looks at how PipeCD for CI/CD works and what to expect if you're migrating from ArgoCD
https://www.admin-it.io/pipecd-for-ci-cd/?utm_source=mam
#PipeCD #ArgoCD #orchestrator #Kubernetes #Linux #containers #K8s

Reproducible ESP32 Firmware Development with Docker and Docker Sandboxes
#Docker #Community #Containers #DockerSandboxes

https://www.docker.com/blog/reproducible-esp32-firmware-development-with-docker-and-docker-sandboxes/

Reproducible ESP32 Firmware Development with Docker and Docker Sandboxes
#Docker #Community #Containers #DockerSandboxes

https://www.docker.com/blog/reproducible-esp32-firmware-development-with-docker-and-docker-sandboxes/

Как я написал PID 1 для контейнеров на чистом ассемблере: x86-64 и ARM64

Не потому, что контейнерному миру срочно нужен ещё один init. Есть Tini, есть docker run --init , и для большинства production-сценариев я бы по-прежнему начал именно с них. Мне скорее хотелось разобрать задачу до самого нижнего уровня: без libc, без runtime, напрямую через Linux syscalls. Заодно проверить, насколько сильно будет отличаться одна и та же реализация на x86-64 и ARM64. В итоге из небольшого эксперимента получился mini-init-asm : PID 1, который запускает приложение в отдельной process group, передаёт сигналы всей группе, собирает zombie-процессы и умеет корректно завершать контейнер с exit code приложения. Позже туда добавились subreaper mode и простой restart-on-crash. А сам проект в итоге доехал сначала до Debian unstable, а затем и до testing. Но началось всё с вопроса: что вообще должен уметь нормальный PID 1 внутри контейнера?

https://habr.com/ru/articles/1069824/

#linux #pid_1 #containers #assembly #x8664 #arm64 #epoll #docker #debian

Yaay 8:30 meeting got cut short since we didnt have much to talk about. So what am I doing with my new fount 25-ish minutes? Working on a CFP submission for @BSidesDE !

Who wants to get hands on with bootc (on an enterprise class linux no less, RHEL), and learn how you can manage your OS like a container? What security benefits are there? Well you could find out!

Anyway, wish me luck!

#bsides #bsidesde #rhel #redhat #bootc #containers

Yaay 8:30 meeting got cut short since we didnt have much to talk about. So what am I doing with my new fount 25-ish minutes? Working on a CFP submission for @BSidesDE !

Who wants to get hands on with bootc (on an enterprise class linux no less, RHEL), and learn how you can manage your OS like a container? What security benefits are there? Well you could find out!

Anyway, wish me luck!

#bsides #bsidesde #rhel #redhat #bootc #containers

ugghhh....just a week after I update my Gentoo containers base stage3 image, there comes the new binutils:2.47.

So that might cause breakage for distcc (binutils and gcc needs to be same on all distcc). Thankfully building process is all tidy'd up now so will update it soon

#gentoo #containers #docker #podman

🚨 Vulnerabilitate critică veche de 18 ani în kernelul Linux permite acces ROOT și evadare din containere!

A fost descoperită o breșă masivă de securitate în kernelul Linux care a rămas nedetectată timp de aproape două decenii. Aceasta le permite atacatorilor să obțină privilegii maxime de sistem (root) și să părăsească mediile izolate precum containerele Docker sau LXC (container escape).

✨ Detaliile vulnerabilității:

⚠️ Impact și vechime:
• Codul vulnerabil este prezent în kernelul Linux de 18 ani, afectând o gamă uriașă de distribuții, de la servere enterprise de producție până la medii de stocare, cloud și dispozitive bazate pe Linux.

🔓 Privilege Escalation & Container Escape:
• Exploatarea permite unui utilizator local neautorizat (sau unui atacator care a compromis o aplicație dintr-un container) să treacă peste barierele de securitate ale kernelului, să obțină drepturi de root pe sistemul gazdă (host) și să acceseze datele altor containere sau ale sistemului principal.

🛡️ Remediere și patch-uri:
• Echipa de dezvoltare a kernelului Linux și marii furnizori de distribuții (Red Hat, Ubuntu, Debian, SUSE) au lansat în regim de urgență patch-uri de securitate pentru a acoperi această breșă.

🛠️ Ce trebuie să faci imediat?

Actualizează sistemul: Rulează o actualizare completă a pachetelor și a kernelului:
• Ubuntu/Debian: sudo apt update && sudo apt dist-upgrade
• RHEL/AlmaLinux/Rocky: sudo dnf update

Repornește serverul / sistemul: Pentru ca noul kernel patch-uit să fie încărcat în memorie, este necesară o repornire (sudo reboot).

O reamintire dură a faptului că chiar și codul matur și intens auditat din lumea open-source poate ascunde vulnerabilități critice pentru o perioadă lungă de timp! 🚀

#Linux #CyberSecurity #KernelVulnerability #Root #Docker #Containers #Linuxiac #TechNews #SysAdmin #OpenSource

🚨 Vulnerabilitate critică veche de 18 ani în kernelul Linux permite acces ROOT și evadare din containere!

A fost descoperită o breșă masivă de securitate în kernelul Linux care a rămas nedetectată timp de aproape două decenii. Aceasta le permite atacatorilor să obțină privilegii maxime de sistem (root) și să părăsească mediile izolate precum containerele Docker sau LXC (container escape).

✨ Detaliile vulnerabilității:

⚠️ Impact și vechime:
• Codul vulnerabil este prezent în kernelul Linux de 18 ani, afectând o gamă uriașă de distribuții, de la servere enterprise de producție până la medii de stocare, cloud și dispozitive bazate pe Linux.

🔓 Privilege Escalation & Container Escape:
• Exploatarea permite unui utilizator local neautorizat (sau unui atacator care a compromis o aplicație dintr-un container) să treacă peste barierele de securitate ale kernelului, să obțină drepturi de root pe sistemul gazdă (host) și să acceseze datele altor containere sau ale sistemului principal.

🛡️ Remediere și patch-uri:
• Echipa de dezvoltare a kernelului Linux și marii furnizori de distribuții (Red Hat, Ubuntu, Debian, SUSE) au lansat în regim de urgență patch-uri de securitate pentru a acoperi această breșă.

🛠️ Ce trebuie să faci imediat?

Actualizează sistemul: Rulează o actualizare completă a pachetelor și a kernelului:
• Ubuntu/Debian: sudo apt update && sudo apt dist-upgrade
• RHEL/AlmaLinux/Rocky: sudo dnf update

Repornește serverul / sistemul: Pentru ca noul kernel patch-uit să fie încărcat în memorie, este necesară o repornire (sudo reboot).

O reamintire dură a faptului că chiar și codul matur și intens auditat din lumea open-source poate ascunde vulnerabilități critice pentru o perioadă lungă de timp! 🚀

#Linux #CyberSecurity #KernelVulnerability #Root #Docker #Containers #Linuxiac #TechNews #SysAdmin #OpenSource

@RockyC Nice stack (virtually and physically)! Wondering which of those two NAS devices is Wrecker and which is Crosshair!

My homelab is 100% #Synology + #unifi from hw standpoint. Running about 90 #containers for all kinds of things among 5 current devices, with 2 more coming within a months time.

Also have one HP just as you for Prox testing but thats about it.

@RockyC Nice stack (virtually and physically)! Wondering which of those two NAS devices is Wrecker and which is Crosshair!

My homelab is 100% #Synology + #unifi from hw standpoint. Running about 90 #containers for all kinds of things among 5 current devices, with 2 more coming within a months time.

Also have one HP just as you for Prox testing but thats about it.

Pullrun: an open-source Project to run OCI images as Linux containers, Firecracker microVMs, or Apple Silicon VMs ; no daemon required, no overlayfs, no separate VM images #Containers #OCI https://github.com/pullrun/pullrun

Pullrun: an open-source Project to run OCI images as Linux containers, Firecracker microVMs, or Apple Silicon VMs ; no daemon required, no overlayfs, no separate VM images #Containers #OCI https://github.com/pullrun/pullrun

🎉 Oh joy, another riveting tale of wrestling with X11! Apparently, all you need is some arcane sed #magic to get your #1980s window system to work with modern #containers. 🥳 Who knew sharing #graphics across hosts could be such a party? 🎈
https://dobrowolski.dev/article/sharing-an-x-server-across-hosts-with-familywild/ #X11 #Party #HackerNews #ngated

🎉 Oh joy, another riveting tale of wrestling with X11! Apparently, all you need is some arcane sed #magic to get your #1980s window system to work with modern #containers. 🥳 Who knew sharing #graphics across hosts could be such a party? 🎈
https://dobrowolski.dev/article/sharing-an-x-server-across-hosts-with-familywild/ #X11 #Party #HackerNews #ngated

🚀 Incus 7.3 a fost lansat: Accelerare GPU partajată și 13 remedieri de securitate! Ghidul și administratorul open-source de containere și mașini virtuale, Incus, ajunge la versiunea 7.3, aducând funcționalități avansate de performanță, opțiuni noi de rețea și o serie importantă de corecții de securitate. ✨ Ce aduce nou Incus 7.3:🎮 Accelerare GPU 3D partajată pentru VM-uri:• Introduce un tip nativ de GPU ce combină virtio-gpu și virglrenderer, permițând mai multor mașini virtuale Linux să partajeze eficient resursele aceleiași plăci grafice, fără a mai fi nevoie de passthrough PCI dedicat. 🛡️ 13 vulnerabilități de securitate rezolvate:• Remediază probleme critice ce puteau permite traversarea directoarelor (path traversal) sau executarea de comenzi prin legături simbolice și fișiere de backup malițioase.⚙️ Administrare directă UEFI NVRAM:• Comandă nouă incus low-level nvram ce le permite administratorilor să modifice ordinea de boot și variabilele de firmware direct din terminal. 🌐 Îmbunătățiri de rețea și BGP:• Suport pentru sesiuni BGP ne-numerotate prin interfețe de rețea (IPv6 link-local), optimizând rutarea adreselor IP către instanțe. 💻 Instalatoare native pentru Windows & macOS:• Pachete de instalare dedicate (MSI și PKG) lansate direct pentru utilizatorii de desktop. Un pas important pentru un management eficient și sigur al mașinilor virtuale și containerelor pe Linux! 🚀 #Incus #Virtualization #Linux #SysAdmin #OpenSource #Containers #VirtualMachines #CloudNative #TechNews

🚀 Incus 7.3 a fost lansat: Accelerare GPU partajată și 13 remedieri de securitate! Ghidul și administratorul open-source de containere și mașini virtuale, Incus, ajunge la versiunea 7.3, aducând funcționalități avansate de performanță, opțiuni noi de rețea și o serie importantă de corecții de securitate. ✨ Ce aduce nou Incus 7.3:🎮 Accelerare GPU 3D partajată pentru VM-uri:• Introduce un tip nativ de GPU ce combină virtio-gpu și virglrenderer, permițând mai multor mașini virtuale Linux să partajeze eficient resursele aceleiași plăci grafice, fără a mai fi nevoie de passthrough PCI dedicat. 🛡️ 13 vulnerabilități de securitate rezolvate:• Remediază probleme critice ce puteau permite traversarea directoarelor (path traversal) sau executarea de comenzi prin legături simbolice și fișiere de backup malițioase.⚙️ Administrare directă UEFI NVRAM:• Comandă nouă incus low-level nvram ce le permite administratorilor să modifice ordinea de boot și variabilele de firmware direct din terminal. 🌐 Îmbunătățiri de rețea și BGP:• Suport pentru sesiuni BGP ne-numerotate prin interfețe de rețea (IPv6 link-local), optimizând rutarea adreselor IP către instanțe. 💻 Instalatoare native pentru Windows & macOS:• Pachete de instalare dedicate (MSI și PKG) lansate direct pentru utilizatorii de desktop. Un pas important pentru un management eficient și sigur al mașinilor virtuale și containerelor pe Linux! 🚀 #Incus #Virtualization #Linux #SysAdmin #OpenSource #Containers #VirtualMachines #CloudNative #TechNews

🦎 Komodo 2.3 a fost lansat: Utilitarul de build & deploy aduce o căutare mai rapidă în containere!

Instrumentul open-source Komodo, conceput pentru a simplifica construirea, gestionarea și orchestrarea containerelor (Docker) pe servere multiple, ajunge la versiunea 2.3, aducând îmbunătățiri mari de performanță și un flux de lucru mai eficient pentru admini și developeri.

✨ Ce aduce nou Komodo 2.3:

⚡ Căutare ultra-rapidă în containere:
• Căutarea și filtrarea prin sute de containere, imagini, volume sau rețele din interfața web este acum de până la câteva ori mai rapidă, datorită optimizărilor aduse motorului de indexare intern.

🐳 Management Docker simplificat:
• Permite vizualizarea resurselor consumate în timp real, gestionarea stack-urilor Docker Compose și inspectarea log-urilor fără întârzieri.

🔄 Automatizări și Deploy-uri mai fluide:
• Procesele de build automatizat (CI/CD ușor) și actualizarea containerelor prin webhook-uri funcționează cu un timp redus de latență.

🎨 Interfață UI/UX rafinată:
• Meniuri ajustate pentru o mai bună vizibilitate pe ecrane de diferite dimensiuni, un control mai facil asupra permisiunilor de acces și un mod întunecat (dark mode) îmbunătățit.

🔒 Securitate și stabilitate sporite:
• Corecții de securitate pe canalele de comunicare dintre nodul central (Komodo Core) și agenții instalați pe servere (Komodo Periphery).

Un instrument extrem de util pentru oricine caută o alternativă lightweight și modernă la dashboard-urile complexe de orchestrare! 🚀

#Komodo #Docker #DevOps #SysAdmin #OpenSource #Containers #SelfHosted #Linux #TechNews

🦎 Komodo 2.3 a fost lansat: Utilitarul de build & deploy aduce o căutare mai rapidă în containere!

Instrumentul open-source Komodo, conceput pentru a simplifica construirea, gestionarea și orchestrarea containerelor (Docker) pe servere multiple, ajunge la versiunea 2.3, aducând îmbunătățiri mari de performanță și un flux de lucru mai eficient pentru admini și developeri.

✨ Ce aduce nou Komodo 2.3:

⚡ Căutare ultra-rapidă în containere:
• Căutarea și filtrarea prin sute de containere, imagini, volume sau rețele din interfața web este acum de până la câteva ori mai rapidă, datorită optimizărilor aduse motorului de indexare intern.

🐳 Management Docker simplificat:
• Permite vizualizarea resurselor consumate în timp real, gestionarea stack-urilor Docker Compose și inspectarea log-urilor fără întârzieri.

🔄 Automatizări și Deploy-uri mai fluide:
• Procesele de build automatizat (CI/CD ușor) și actualizarea containerelor prin webhook-uri funcționează cu un timp redus de latență.

🎨 Interfață UI/UX rafinată:
• Meniuri ajustate pentru o mai bună vizibilitate pe ecrane de diferite dimensiuni, un control mai facil asupra permisiunilor de acces și un mod întunecat (dark mode) îmbunătățit.

🔒 Securitate și stabilitate sporite:
• Corecții de securitate pe canalele de comunicare dintre nodul central (Komodo Core) și agenții instalați pe servere (Komodo Periphery).

Un instrument extrem de util pentru oricine caută o alternativă lightweight și modernă la dashboard-urile complexe de orchestrare! 🚀

#Komodo #Docker #DevOps #SysAdmin #OpenSource #Containers #SelfHosted #Linux #TechNews

DevOP 101

Development is not something that one finishes learning. As it is with most academia, learning in general is not something we ever finish. We just keep building onto our knowledge base and sometimes refactoring our knowledge to meet new ideologies and principles. With that said there are many great books that teach us valuable skills though they were written 5 to 10 years ago and their tool chains are outdated by today's standard. Sometimes the changes are mild enough for us to still work with the book despite the older tool chains. Sometimes the changes are so radical that it is more work to try to adapt the source to our modern tool chains then to just get a different resource. Though, not all books are of the same quality. So when you find a good one it is nice to use that book. Learn the techniques and then worry about adapting those techniques to a modern tool chain once they are fully understood.

In this day and age this challenge has never been easier for a developer to overcome. I am a Fedora user so I use podman in these examples though you could just as easily use docker if you feel it necessary to do so. Okay, so we are looking at the Packt book 'C++ Programming for Linux Systems: Create robust enterprise software for Linux and Unix-based operating systems' Upon examining the introduction we realize that the book is showing its age and the authors used Mint 21 with the gcc 12.x tool chain. Yeah, that is a bit old for today's standards though still completely usable. There is nothing taught in the book that will not be valuable by today's standards. Yet trying to work with the books source on a modern system could be a challenge one does not wish to accept while learning the material. Our solution? Build an OCI container with the author's suggested tool chain installed so that we know the book source should build without issues.

It is a good DevOP practice to setup containers for development in any case. So we can effectively reduce the 'It worked on my machine' phenomenon. So let us setup a Container for our book. First you should navigate to the books source code, in this case it is on GitHub, and clone it to a directory on your system. We are going to reference this directly in our Container so we will want it prepared before we begin. For our book in this example the source is here.

Okay, we have the source ready in a directory so let us build a container for working with the book source code! The following is a Containerfile (which can also be named Dockerfile as podman will accept either).
Containerfile

# Use the official standalone Linux Mint 21 base runtime image
FROM docker.io/linuxmintd/mint21-amd64:latest

# Prevent interactive prompts during package installations
ENV DEBIAN_FRONTEND=noninteractive

# Update repository lists and install the explicit GCC 12 toolchain and utilities
RUN apt-get update && apt-get upgrade -y && apt-get install -y \
    gcc-12 \
    g++-12 \
    make \
    git \
    gdb \
    valgrind \
    sudo \
    && echo "developer ALL=(ALL) NOPASSWD:ALL" >> /etc/sudoers \
    && rm -rf /var/lib/apt/lists/*

# Link system compiler targets explicitly to the version 12 toolchain
RUN update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-12 100 \
    && update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-12 100

# Create a non-root development user matching standard Linux host UID 1000
RUN useradd -m -u 1000 -s /bin/bash developer

# Establish the persistent volume target folder 
WORKDIR /workspace
RUN chown developer:developer /workspace

# Relinquish root execution and switch permanently to the non-root profile
USER developer

# Set the default shell behavior
CMD ["/bin/bash"]

podman run -it --name mint21-book-dev \
  -v /path/to/your/local/book-code:/workspace:Z \
  mint21-gcc12-env

We now have a fully provisioned OCI container that can be used with either podman or docker to provide the tool chain our book uses. This will allow us to focus on the content of the book rather than adapting code examples to our tool chain. That is a project we can work on after the concepts in the book are properly understood. If you would like to learn more about building your own containers for your development needs then I highly recommend the book Podman for DevOps

Unus Nemo

Tips & Donations

#DevOPS #Containers #podman

DevOP 101

Development is not something that one finishes learning. As it is with most academia, learning in general is not something we ever finish. We just keep building onto our knowledge base and sometimes refactoring our knowledge to meet new ideologies and principles. With that said there are many great books that teach us valuable skills though they were written 5 to 10 years ago and their tool chains are outdated by today's standard. Sometimes the changes are mild enough for us to still work with the book despite the older tool chains. Sometimes the changes are so radical that it is more work to try to adapt the source to our modern tool chains then to just get a different resource. Though, not all books are of the same quality. So when you find a good one it is nice to use that book. Learn the techniques and then worry about adapting those techniques to a modern tool chain once they are fully understood.

In this day and age this challenge has never been easier for a developer to overcome. I am a Fedora user so I use podman in these examples though you could just as easily use docker if you feel it necessary to do so. Okay, so we are looking at the Packt book 'C++ Programming for Linux Systems: Create robust enterprise software for Linux and Unix-based operating systems' Upon examining the introduction we realize that the book is showing its age and the authors used Mint 21 with the gcc 12.x tool chain. Yeah, that is a bit old for today's standards though still completely usable. There is nothing taught in the book that will not be valuable by today's standards. Yet trying to work with the books source on a modern system could be a challenge one does not wish to accept while learning the material. Our solution? Build an OCI container with the author's suggested tool chain installed so that we know the book source should build without issues.

It is a good DevOP practice to setup containers for development in any case. So we can effectively reduce the 'It worked on my machine' phenomenon. So let us setup a Container for our book. First you should navigate to the books source code, in this case it is on GitHub, and clone it to a directory on your system. We are going to reference this directly in our Container so we will want it prepared before we begin. For our book in this example the source is here.

Okay, we have the source ready in a directory so let us build a container for working with the book source code! The following is a Containerfile (which can also be named Dockerfile as podman will accept either).
Containerfile

# Use the official standalone Linux Mint 21 base runtime image
FROM docker.io/linuxmintd/mint21-amd64:latest

# Prevent interactive prompts during package installations
ENV DEBIAN_FRONTEND=noninteractive

# Update repository lists and install the explicit GCC 12 toolchain and utilities
RUN apt-get update && apt-get upgrade -y && apt-get install -y \
    gcc-12 \
    g++-12 \
    make \
    git \
    gdb \
    valgrind \
    sudo \
    && echo "developer ALL=(ALL) NOPASSWD:ALL" >> /etc/sudoers \
    && rm -rf /var/lib/apt/lists/*

# Link system compiler targets explicitly to the version 12 toolchain
RUN update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-12 100 \
    && update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-12 100

# Create a non-root development user matching standard Linux host UID 1000
RUN useradd -m -u 1000 -s /bin/bash developer

# Establish the persistent volume target folder 
WORKDIR /workspace
RUN chown developer:developer /workspace

# Relinquish root execution and switch permanently to the non-root profile
USER developer

# Set the default shell behavior
CMD ["/bin/bash"]

podman run -it --name mint21-book-dev \
  -v /path/to/your/local/book-code:/workspace:Z \
  mint21-gcc12-env

We now have a fully provisioned OCI container that can be used with either podman or docker to provide the tool chain our book uses. This will allow us to focus on the content of the book rather than adapting code examples to our tool chain. That is a project we can work on after the concepts in the book are properly understood. If you would like to learn more about building your own containers for your development needs then I highly recommend the book Podman for DevOps

Unus Nemo

Tips & Donations

#DevOPS #Containers #podman

Komodo 2.3 introduces paginated resource and container lists, improved search, server-side sorting, and better UI responsiveness.
https://linuxiac.com/komodo-2-3-build-and-deploy-tool-released-with-faster-container-search/

#opensource #containers

Komodo 2.3 introduces paginated resource and container lists, improved search, server-side sorting, and better UI responsiveness.
https://linuxiac.com/komodo-2-3-build-and-deploy-tool-released-with-faster-container-search/

#opensource #containers

Our next #JCON2026 session is live: 'Never Trust a Monkey: The Chasm, the #Craft, and the #Chain of #AI Assisted Code' with Baruch Sadogursky

We’re in the midst of another abstraction leap.
Just like #compilers #cloud and #containers before it, …

Grab your coffee and hit play: https://youtu.be/PUMlajRE-2s

Our next #JCON2026 session is live: 'Never Trust a Monkey: The Chasm, the #Craft, and the #Chain of #AI Assisted Code' with Baruch Sadogursky

We’re in the midst of another abstraction leap.
Just like #compilers #cloud and #containers before it, …

Grab your coffee and hit play: https://youtu.be/PUMlajRE-2s

@bupd
@wamserma
@jarkko

Upon some pondering in the bootc 's goals : https://containers.github.io/bootable/

I fell in love with nix and nixos a lot more again❤️

Nix and NixOS doing bootc's goals for
long time with it's fundamental design. I request people using bootc please check out the awesome tech called as Nix and NixOS. It does more than what bootc 's goals are in a much more elegant way.

Why nix have to be this good😭😭❤️❤️

#nix #nixos #bootc #containers #boot

@wamserma @bupd @jarkko

Actually on some closer look at bootc 's aim, it was pretty what nixos does already. They are trying to figure out through containers way. Those people in bootc will love Nix if they understand that their goals has been already met years ago through Nix for not just nixos, but also for various other projects like nix shells, packaging, etc etc
#bootc #nixos #nix #containers

Hi All
Today @bupd showed me what #bootc is. Honestly I find it cool, even though I'm yet to find it's use case.
But I wanna try running bootc from my #NixOS. So far with quick online search, I couldn't find any.
Also he mentioned some problems of making nixos based bootc images if I understand it correctly.

Will ponder and explore these.
I'm thinking of 2 ways:
1) adding bootc image to bootloader menu
2) using nixos specialisations to create bootc or bootc like environment
#containers

Hi All
Today @bupd showed me what #bootc is. Honestly I find it cool, even though I'm yet to find it's use case.
But I wanna try running bootc from my #NixOS. So far with quick online search, I couldn't find any.
Also he mentioned some problems of making nixos based bootc images if I understand it correctly.

Will ponder and explore these.
I'm thinking of 2 ways:
1) adding bootc image to bootloader menu
2) using nixos specialisations to create bootc or bootc like environment
#containers

Jails, Not Containers: FreeBSD Isolation Done Right – Umair Khurshid | Klara Systems

<https://klarasystems.com/articles/jails-not-containers-freebsd-isolation-done-right/>

Containers play a major role in modern infrastructure, but they are not the right answer for every workload. This article explores how FreeBSD jails provide purpose-built isolation, predictable security boundaries, and deep ZFS integration—making them ideal infrastructure-grade services where stability is essential. …

Via <https://indieweb.social/@jbz/116907602232548204> | <https://billboard.bsd.cafe/post/857> | <https://www.reddit.com/r/freebsd/comments/1v5nkno/jails_not_containers_freebsd_isolation_done_right/>

#FreeBSD #jails #Linux #containers

Jails, Not Containers: FreeBSD Isolation Done Right – Umair Khurshid | Klara Systems

<https://klarasystems.com/articles/jails-not-containers-freebsd-isolation-done-right/>

Containers play a major role in modern infrastructure, but they are not the right answer for every workload. This article explores how FreeBSD jails provide purpose-built isolation, predictable security boundaries, and deep ZFS integration—making them ideal infrastructure-grade services where stability is essential. …

Via <https://indieweb.social/@jbz/116907602232548204> | <https://billboard.bsd.cafe/post/857> | <https://www.reddit.com/r/freebsd/comments/1v5nkno/jails_not_containers_freebsd_isolation_done_right/>

#FreeBSD #jails #Linux #containers

Conferences are containers for ideas. Especially when they're places where participants share and co-create ideas, rather than just listen.

https://www.conferencesthatwork.com/index.php/event-design/2013/08/conferences-are-containers-for-ideas

#meetings #ideas #containers #EventDesign #events #conferences #eventprofs

Conferences are containers for ideas. Especially when they're places where participants share and co-create ideas, rather than just listen.

https://www.conferencesthatwork.com/index.php/event-design/2013/08/conferences-are-containers-for-ideas

#meetings #ideas #containers #EventDesign #events #conferences #eventprofs

Reading up a bit on Linux containers

I wonder if the efficiency of them is close to that of freeBSD jails

https://linuxcontainers.org/

#Containers #VM #freeBSD #jails #programming #XEN #networking

Reading up a bit on Linux containers

I wonder if the efficiency of them is close to that of freeBSD jails

https://linuxcontainers.org/

#Containers #VM #freeBSD #jails #programming #XEN #networking

From the .NET blog...

In case you missed it earlier...

.NET 11 Preview 6 is now available!
https://devblogs.microsoft.com/dotnet/dotnet-11-preview-6/ #dotnet #NETMAUI #ASPNETCore #csharp #Containers #EntityFramework #fsharp #NET11 #Featured

.NET 11 Preview 6 is now available!
https://devblogs.microsoft.com/dotnet/dotnet-11-preview-6/

#microsoft #NET #NET_MAUI #ASP_NET_Core #C #Containers #Entity_Framework #F #NET_11 #Featured

From the .NET blog...

.NET 11 Preview 6 is now available!
https://devblogs.microsoft.com/dotnet/dotnet-11-preview-6/ #dotnet #NETMAUI #ASPNETCore #csharp #Containers #EntityFramework #fsharp #NET11 #Featured

#NYC #Manhattan upper #WestSide and #EastSide near #CentralPark will lose the most parking spots -
#NewYorkCity says they're not taking parking, they're "repurposing public space" for the public good.
They say having to pay for parking a few days a month, at $270/ month, is a fair expectation for area #residents; my car's in Weehawken for $250/ month, the first stop on the bus from #PortAuthority, so I'm doin' pretty good I think.
#trash #bins #containers #rodent #rats
https://gothamist.com/news/parts-of-manhattan-to-sacrifice-10-of-street-parking-as-nyc-installs-new-trash-bins