[ggm]

I think they understate the importance of accepting OCI and Dockerfile semantics as a path to an external "run one of these" and having it actually emerge as a jail based outcome.

I get saying "we don't need these additional layers/abstractions" but what it ignores is me saying "I want to run this code, and what I have is a suite of Docker based behaviour and I want a low friction path to use that Docker compose method, to get where I want"

They also haven't yet addressed how things re-scale sideways. Pods, and scaling is why people wind up behind traefik or caddy, fronting a service. It's not because the service lies in RFC1918 (how I wish they had written kubernetes to V6 native) it's because the service is being delivered by multiple discrete runtime states "inside" and scales horizontally.

[lstodd]

It's a different operating system. You can't point at a dockerfile, say "port this please from linux-such-and-such to FreeBSD" and expect it to work every time. There are nuances even with linux-compat.

Contrary to popular belief load-balance/scaleout is orthogonal to containers (and k8s is only one of the ways to go about it), so obviously it's not discussed in an article about containers.

[nine_k]

Very often you can, or could, because the software is portable (e.g. Node or Python or Postgres), and / or platform-independent (e.g. written in JS, Python, bash, etc).

In my practice it was completely normal to build things inside a container to be deployed on Linux using the same sources and basically the same package names and versions as used on a developer macOS machine (which is BSD-like enough down below).

[trashb]

> macOS machine (which is BSD-like enough down below)

That's like saying an Ubuntu .deb will work on Gentoo because it's all Linux anyway. It's not that simple. There is dependencies and there are differences in the packages, package managers and surrounding system for a reason. It's not 1:1. Perhaps the naming scheme happened to line up for the packages you where using, but this should be considered not assumed.

It would be nice if there was some sort of translator that could handle "most common cases". I think it would improve the usability of Jails. Perhaps that would require someone to keep a list of packages mapping certain packages between operating systems.

Something like "apt install python3-serial" -> "pkg install py311-pyserial" may suffice.

For anyone that would use something like that, you should implement a prototype, publish it and perhaps someone else will build upon what you started!

[Joker_vD]

> It's not that simple.

It would tremendously benefit almost everyone if it were.

> There is dependencies and there are differences in the packages, package managers and surrounding system for a reason.

Yeah, the NIH syndrome. And sometimes, of course, there are decent technical reasons as well.

[LoganDark]

This is called https://brew.sh

[sharts]

Isn’t podman already supported? I wouldn’t be surprised that there already exist tools that will jail-ify that as well.