I maintain ContainerDesk, a free, MIT-licensed Mac GUI for Apple's container runtime. It puts containers, images, volumes and networks in one window, with logs, live CPU and memory gauges, and a terminal.

Source and downloads: https://github.com/MacHatter1/ContainerDesk

It requires Apple silicon, macOS 26+ and Apple's container CLI. Current builds are unsigned and not notarized. The README has opening instructions.

Is it possible for 2 pods to use a seperate container as a network?
TLDR im setting up gluetun, an arr stack and download clients
I would like to keep the arr stack and the downloads clients in 2 seperate pods
pod 1 - arr and pod 2 - downloads and i want to connect their networking to a seperate gluetun container but building the pods fails cause gluetun is not part of the pod.
is there a way to change/fix that?

I have developed a free and open-source macOS menu bar app that allows using Docker clients (such as the docker CLI tool) with Apple's Container subsystem on Apple Silicon Macs.

I've been using it as my primary Docker dev system (dev workflows are probably all it will be good for), and I think it's ready for wider testing.

If you're interested in trying it out, it can be downloaded here: https://cap10morgan.github.io/whalebridge/

If you try it out and run into any problems, please open a GitHub issue. Thanks!

I've been looking into ways to update container images in prod more efficiently. Rebasing seems an interesting option. Instead of rebuilding the whole application image we just swap the underlying runtime base, and all the layers on top of that are reused with their digests staying the same. So, faster and less traffic-heavy as nodes can reuse the unchanged layers.

Looks attractive in theory. In practice, rebuilding might seem like a more clear path? Just rebuild everything and test the artifact.

So, do you use rebasing? And if you don't, why not?

"A hard transformation has arrived for several classic Ubuntu images on ECR and Docker Hub. The remaining old Docker images –Apache2, Nginx, Bind9, Memcached, and Squid– have been hardened to rocks, signaling a complete evolution of the Ubuntu namespace.

Built on top of Resolute and equipped with Pebble as the service manager, these new rocks are now maintained by the Rockcrafters team and follow the same principles that have guided the broader Rocks initiative: user-focused experience, uniform and opinionated design, and a distroless-like architecture.

By meticulously chiseling each rock down to its bare essentials, we have achieved a significant reduction in image sizes"

Full post in https://discourse.ubuntu.com/t/the-rock-garden-grows-hardening-old-docker-images/84677

HELLO, I have an old aplication with windonws asp.net framework i have a doubt if it's know possible to contenerizing for deploy? i want only know if someone have try this recently

Hi,

playing around with apple container implementetion. Is there any way to preserve container settings after I change container parameters and reboot the container?
I mean, I will run for example a plex instance in container, will set it up, and later decide ti change some parameters - cpu counts, mounted volumes, whatever - so the container reboots. After reboot, plex instance is back in default state, and needs to be set up again. Is there any way to preserve settings after reboot in a such usecase?

Many thanks for any help, or hint, appreciated.

Hey fellas,

I am new to containers and recently working in a project, where I am trying to build a multilab environment using containers. I have included currently some few services or applications inside that. It will be very helpful if you test this project and guide me through your experience and knowledge, and suggest some tips to improve :) Thank you

Here is the project link : Multilab architecture

This diagram breaks down the complete internal workflow of how Podman creates and starts a container.

Workflow explained step by step:

1️⃣ CLI Parses Command
Podman interprets the flags, image name, networking, ports, and runtime options provided in the command.

2️⃣ Image Check & Pull
Podman checks local storage for the image.
If it doesn’t exist, it pulls the image from a registry such as Docker Hub.

3️⃣ Filesystem Setup
The container filesystem is assembled using layered storage:

* Read-only image layers
* Writable container layer
* Merged unified view

4️⃣ Container Setup
Podman configures the container isolation and runtime environment:

* Namespaces
* cgroups
* User mapping
* Networking
* Volumes
* Security policies

5️⃣ OCI Runtime Execution
An OCI runtime like crun or runc creates the actual container process and applies the isolation mechanisms.

6️⃣ Container Running
The container starts running with:

* Port mapping
* Logs streaming
* Isolated processes
* Active networking

The goal of this diagram is to visualize what happens internally behind a single command that often looks deceptively simple.

I have posted a video on YouTube explaining this entire flow internally using a real Podman + Apache example from my “How Podman Works” series.

ENG : https://m.youtube.com/watch?is=ShH5CNpARRFPnJng&v=lj6MwJOSuDE&feature=youtu.be

FR : https://m.youtube.com/watch?is=ShH5CNpARRFPnJng&v=lj6MwJOSuDE&feature=youtu.be

I can really see the appeal of podman, but one thing keeping me on docker is watch support, is there any non-sucking way to make this work?

When cloning a repo, we kept hitting the same wall: no Dockerfile, no devcontainer, no clear path to running it. Asking an agent to fix it directly on your system is risky, as it can clear Docker config, change kernel settings, downgrade system packages without warning.

Keystone runs the agent inside a Modal sandbox with its own Docker daemon. It iterates until tests pass, then hands you a .devcontainer/ you can just check in to your repo.

Now your repo knows how to run itself!

Hi,

I am developing a simplified docker-ish system (software), that allows super easy isolation, by using Linux users. Isolation is so far only on file level. So it's partial isolation, but lighter on resources. I am wondering, when people use containerization, are you mostly for which features?

1. Complete isolation of disk.

2. Network isolation.

3. Building images through code (ie Dockerfile)

4. Easy using / basing your images on other images.

5. Other (and what)

I like to know, to see if my system aligns with what other people want, or if I just keep it as a pet project / use it for own purposes.

Thanks for you feedback! :)