edu4rdshl

Any issues/features requests are welcome. Thanks for bringing it up here.

Hi, nspawn maintainer here, that's not the case. I have been working with code/software architecture/design since a very long time before agentic coding was a thing. nspawn uses AI to help write code (the README has a clear AI usage disclosure) but every change is reviewed by me.

The architecture decisions, etc are dictated by me as well :)

If you have any suggestions, etc, they are welcome.

nspawn maintainer here. Yes, it has been done with the help of AI (the README has a clear AI usage disclosure), but I have been writing Rust code since a very long time ago, before agentic coding was a thing (you can check my GH profile). Every change is reviewed by me, and the architecture/implementation is dictated by me as well.

Ideas/issues/PRs are welcome.

TLDR: It's an old initiative to make using systemd-nspawn much easier, including a hub of images compiled with mkosi and signed using Sigstore.It was put on hold about two years ago, but we've revived it. The hub is available at https://hub.nspawn.org/home

The current CLI implementation matches most of the Docker's used features, such as search/pull/exec/run/network/cp/events/stats/build, respecting the entrypoints, propagating labels, ports and resource limits management, and more. Support for other registries such as DockerHub and any OCI registry has been added as well.

Documentation can be found in: https://nspawn.org/docs/

Edit: as an additional note, everything is exposed through a D-Bus API so that any other client/UI can make their own implementation.

It's fun how most of the complaints are like "it works fine on Gnome but I will still blame Wayland because my tiling WM doesn't support it". So maybe try using a proper Wayland implementation

The Chrome crashes when resizing a window doesn't makes any sense, apart from being a WM fault. The Xwayland scaling, again, has native scaling support on Gnome. Same for the monitor resolution problem (which he acknowledged). Same for font rendering. Idk.

> And Google helped it happen No, it doesn't, you were just stupid. That field has always been modifiable.

Every action you did is what you hear multiple times every week about people falling in pishing, and you continued.

Finally, it was just some crypto shit so not a big deal.

It's... weird, and even absurd at some point.

You can continue using `docker-compose` (the provider) with `podman compose`. It's the default provider if installed.

A small article that will reply most questions that arise when migrating from Docker to Podman.