#poudriere jail -l freebsd_141_2 14.1-RELEASE-p3 amd64 http 2024-08-11 12:51:15 /usr/local/poudriere/jails/freebsd_141_2 Then # poudriere bulk -j freebsd_141_2 -f /usr/local/etc/poudriere.d/port-list [00:00:00] Creating the reference jail... done [00:00:00] Mounting system devices for freebsd_141_2-default [00:00:00] Warning: Using packages from previously failed, or uncommitted, build: /usr/local/poudriere/data/packages/freebsd_141_2-default/.building [00:00:00] Mounting ports from: /usr/local/poudriere/ports/default [00:00:00] Mounting packages from: /usr/local/poudriere/data/packages/freebsd_141_2-default [00:00:00] Mounting distfiles from: /usr/ports/distfiles [00:00:00] Appending to make.conf: /usr/local/etc/poudriere.d/make.conf /etc/resolv.conf -> /usr/local/poudriere/data/.m/freebsd_141_2-default/ref/etc/resolv.conf [00:00:00] Starting jail freebsd_141_2-default [00:00:00] Error: Unable to execute id(1) in jail. Emulation or ABI wrong. [00:00:00] Cleaning up [00:00:00] Unmounting file systems Exiting with status 1 The "funny thing" is it worked yesterday flawlessly and as one can see the jail says "amd64" however i get: [00:00:00] Error: Unable to execute id(1) in jail. Emulation or ABI wrong.
Any updates?
Today I received the exact same message (and it worked yesterday). I could create and delete jails, but could not run pkgclean or bulk commands. Since I run poudriere in its own jail, it was enough to restart the jail. Yet I'd be curious to pinpoint the cause.
(In reply to ml from comment #2) I deleted the Jail with "-C all" recreated it, i could also run pkgclean even update the jail. Then i "restored" all configs to vanilla, but the problem persists when i start building the ports, i also could not find many helpful posts on the inter-webs (just delete the jail etc). Again whats crazy is that it worked one day before, and without any changes the next day it did not.
Happened again this night: a batch file should have run poudriere with clean/bulk on different jails. Worked for some, then suddenly stopped. Solving was as easy as restarting Poudriere's own jail, but the packages I was expecting this morning are not there :( Twice in a relatively short timespan means this must have begun after an upgrade (either from 14.0 to 14.1 or a later patchlevel).
So is that ticket even read or do i have to open a "Issue" on github -> instructions unclear ;)
Happened again today. One interesting thing, though, is that, in another jail on the same host, I've been intermittently unable to start rdnsbld when it's configured to be chrooted (which is by default). Again, waiting a couple of days or restarting the outer jail solves. It's a long shot, by I suspect there might be a common root between the two. Are you using poudriere within a jail?
(In reply to ml from comment #6) No poudriere runs directly on host (no poudriere jail)
ping
Works again since last update