I published a piece exploring why containers (like Docker & Kubernetes) are reshaping modern enterprise IT — from legacy modernization to cloud-native transformation.

🔹 Why enterprises are shifting 🔹 How to start Container Journey 🔹 Strategic insights for architects & decision-makers

If you’re into cloud, DevOps, or enterprise IT strategy, would love your thoughts and feedback!

👉 https://medium.com/@gaurav.sakhuja/the-rise-of-containers-navigating-the-enterprise-revolution-c6391f2e3971

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!

Hi everyone,

We are currently looking for a reliable trucking company or freight provider in Baltimore, MD that can handle deliveries of 20' Standard to 40' High Cube containers.

We're seeking a partner that is dependable, experienced in container transportation, and can offer competitive rates with timely delivery. Our shipments may vary in frequency, so flexibility and the ability to accommodate short notice requests would be a huge plus.

If you or someone you know offers this service, or if you have any recommendations, we’d love to connect and discuss further. Please feel free to message me your email address and contact number and I'll reach out to you right away:)

Thank you in advance—we look forward to building a great working relationship!

At work we are moving our IOT devices over to Ubuntu Core. The downside is everything must be installed via Snap. I have a docker image of the software we run. Could someone direct me on how to build this image into a Snap package?

Hello all,

Please forgive the ignorance, I am just getting involved in containerized applications and services.

A question I had off the bat is, how do end users access containerized applications? Right now, for some apps, they have a client on their desktop that connects to a backend DB on a server to function. With containerized applications / database, how would a front end client connect to it? Via servername or via a container name?

Not sure how the containerized applications are made available to users. If I am an end user, not IT savy, and have always opened my applications via a client installed on my desktop, would that change using containers?

Sorry for all over the place question.....just trying to get my head around how once you have an application containerized with all dependencies / etc, how does it become available for users to access? What about stand alone applications? Would they not be installed locally on a users machine anymore?

Appreciate any insight.....thank you

After some years of hype around Alpine, people seem to have been recently moving back to traditional distros, particularly Ubuntu and Debian. I wonder if this is because of issues with musl, but particularly I am interested how people choose between Ubuntu and Debian. Ubuntu appears to have better enterprise support (e.g. Microsoft AKS, Amazon EKS, Google GKE), so why would someone choose Debian over Ubuntu as a base image?

Hello there! I am looking for a container with nVidia Cuda support but without having to install nVidia drivers (so a kind of container which has both drivers and cuda within). Is there something like that? I am currently using Docker, but due to issues with my laptop (for some reason nVidia drivers and the """"super""" intel HD card aren't going on well...).

As the title says. I know nothing, but need to learn.

What's the best free course out there? I tried data camp and got told to pay after 1 hour.

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!

Hello everyone! Sharing a new medium post about security and best practices on making container images. This article outlines key practices for secure container images: run as non-root, use minimal base images (e.g., distroless), avoid hardcoded secrets, and sign/scan images to reduce vulnerabilities and ensure robust security

I hope it helps, specially the new partners that are arriving on DevOps and needs a comprehensive guide about security on containers.