poudriere VS docker-debian-artifacts

poudriere is a powerful port/package build and test system with a focus on package production and bulk building for FreeBSD. This easy-to-use, parallelized solution relies solely on the base system and can build the entire portstree. Supports building packages for different FreeBSD versions, and ensures compatibility with any package management tool by organizing packages in an identical layout to official mirrors. qci considers it a favorite tool.

poudriere(8) command synonyms: jail, jails … · Issue #1053 · freebsd/poudriere

95% of the time the only thing you have to do is install a package and enable the service. So what's the value in having a centralized repository of pre-configured images? Sure, if you want to roll out an image to thousands of servers - make an image using poudriere image](https://github.com/freebsd/poudriere/wiki/poudriere-image.8-devel) and send them out. It's not really any easier - and is definitely not better - to use an image that someone else made.

> pkg is an amazing system that beats dpkg or rpm

What's your reasoning for this statement? I find poudriere[1] handy for compiling one's own packages from ports configured to fit one's goals, but I see nothing outstanding in plain pkg.

It has issues when there's an IPv6 address up (even link-local) but no egress v6 routing. It would hang and wait for a timeout when an IPv6 address is selected from resolved addresses. After a timeout - pkg connects to v4 endpoint but if there's several packages to be downloaded, it can fall back to trying to connect to v6 with the next package.

On the other hand, I've recently had Ubuntu 22.04 register Python-related packages which were not successfully installed, resulting in all dpkg/apt/apt-get commands failing due to py3clean script throwing trackbacks, until /var/lib/dpkg/status was edited and these packages were in fact installed and then removed.

[1] https://github.com/freebsd/poudriere/wiki

poudriere-devel has a bug where it tries to delete the incorrect zpool when building a zfs image fails. There's a pull request that addresses it, but I have no idea when that will get merged. I also don't know how long it will be before there's a new poudriere release after it gets merged. The current ports version was last updated in 2022-09, so it could be months.

I use this with Poudriere to speed up my FreeBSD pkg host building multiple Sets of ports https://github.com/freebsd/poudriere/wiki/ccache

Also jails is a terrific concept with poudriere and bastille

https://github.com/freebsd/poudriere/wiki/ and more.

What's different between debian:bullseye-slim and debian:bullsye (assuming you are talking about https://hub.docker.com/_/debian)

let me try to answer/research this question myself to find the answer/go on this journey:

takes me to

non slim: https://github.com/debuerreotype/docker-debian-artifacts/tre...

slim: https://github.com/debuerreotype/docker-debian-artifacts/tre...

https://github.com/debuerreotype/docker-debian-artifacts/blo... versus https://github.com/debuerreotype/docker-debian-artifacts/blo...

two files are identical

so at a quick glance i have no clue what is going into rootfs.tar.xz that makes one slim and one not

go to google:

https://stackoverflow.com/questions/59794891/how-does-debian...

"just using an elixir docker image": [elixir](https://github.com/erlef/docker-elixir/blob/b108e93389b820554ad9f1e8e07001ed8186d230/1.14/Dockerfile) FROM [erlang:25](https://github.com/erlang/docker-erlang-otp/blob/3e60071a7f14aefe202b602aec0893678d0a0069/25/Dockerfile) FROM [buildpack-deps:bullseye](https://github.com/docker-library/buildpack-deps/blob/65d69325ad741cea6dee20781c1faaab2e003d87/debian/bullseye/Dockerfile) FROM [buildpack-deps:bullseye-curl](https://github.com/docker-library/buildpack-deps/blob/98a5ab81d47a106c458cdf90733df0ee8beea06c/debian/bullseye/curl/Dockerfile) FROM [debian:bullseye](https://github.com/debuerreotype/docker-debian-artifacts/blob/fe5738569aad49a97cf73183a8a6b2732fe57840/bullseye/Dockerfile). wtf is even running on that thing?

FROM scratch ADD rootfs.tar.xz / CMD ["bash"] https://github.com/debuerreotype/docker-debian-artifacts/blob/686d9f6eaada08a754bc7abf6f6184c65c5b378f/bullseye/slim/Dockerfile

Is it the 64 vs 32 bit time calls possibly? Like this: https://github.com/debuerreotype/docker-debian-artifacts/issues/106 What happens if you run the date command from inside the container?