Image builds run their RUN steps on pasta, and every build failure keeps its real error (issue 1703)

Conversation 1 Commits 2 Files Changed 10

+230 -40

2 Commits

Author	SHA1	Message	Date
jschoubben	8c5f27627b	mesh-build-image: give a RUN step pasta's network, since the default netavark bridge cannot be set up rootless (issue 1703) mesh/delivery merged: source.main moved to novox/mesh-catalog@6b6d5cba7195 Details mesh/check checking 8c5f27627b67 on 6b6d5cba7195 Every RUN failed before it started: 'setup network: netavark: nftables error ... Could not process rule'. Reproduced on shanks with buildah 1.45.2, a clean environment and a private XDG_RUNTIME_DIR; --network pasta builds, and reaches the network from a RUN. The sysrq integration row now fails if the RUN never started.	2026-10-26 15:23:19 +01:00
jschoubben	98c66fb1e4	Build modules: a failed command's reason says its error, not its last progress line (issue 1703) buildah writes STEP lines on stdout and its error on stderr, so the last line of both hid every image build's cause. mesh-build-image's reason is now stderr's last lines (600 bytes) with the exit status, and the journal gets both tails; mesh-build-node keeps stderr's end and stdout's start apart; mesh-build-go's cause skips go build's '# package' line.	2026-10-26 15:21:01 +01:00

Author

SHA1

Message

Date

jschoubben

8c5f27627b

mesh-build-image: give a RUN step pasta's network, since the default netavark bridge cannot be set up rootless (issue 1703)

mesh/delivery merged: source.main moved to novox/mesh-catalog@6b6d5cba7195

Details

mesh/check checking 8c5f27627b67 on 6b6d5cba7195

Every RUN failed before it started: 'setup network: netavark: nftables error ... Could not process rule'. Reproduced on
shanks with buildah 1.45.2, a clean environment and a private XDG_RUNTIME_DIR; --network pasta builds, and reaches the
network from a RUN. The sysrq integration row now fails if the RUN never started.

2026-10-26 15:23:19 +01:00

jschoubben

98c66fb1e4

Build modules: a failed command's reason says its error, not its last progress line (issue 1703)

buildah writes STEP lines on stdout and its error on stderr, so the last line of both hid every image build's cause.
mesh-build-image's reason is now stderr's last lines (600 bytes) with the exit status, and the journal gets both tails;
mesh-build-node keeps stderr's end and stdout's start apart; mesh-build-go's cause skips go build's '# package' line.

2026-10-26 15:21:01 +01:00

Image builds run their RUN steps on pasta, and every build failure keeps its real error (issue 1703) #502