On Tue, Mar 21, 2023 at 09:05:12AM -0500, Eric Blake wrote:
$ podman build -f ci/containers/alpine-edge.Dockerfile -t libnbd-alpine-edge
You usually shouldn't need this step when reproducing a problem
on CI. Instead just use the container that gitlab has published
under the project's registry
For any job eg
https://gitlab.com/nbdkit/libnbd/-/jobs/3973002673
you'll see at about line 7/8 in the log a line like
Using Docker executor with image
registry.gitlab.com/nbdkit/libnbd/ci-alpine-edge:latest
That image URL is accessible remotely on your local dev machine eg
podman run -it
registry.gitlab.com/nbdkit/libnbd/ci-alpine-edge:latest
You should only need to do 'podman build' if you're debugging a suspected
problem with the container image itself.
$ podman run -it --rm --userns=keep-id -v .:/repo:z -w /repo
libnbd-alpine-edge bash
$ ./configure
$ make check
$ grep tmpd= lib/test-suite.log
+ tmpd=/tmp/tmp.EMgKeF
$ /tmp/tmp.EMgKeF/bin/f 1 + 1
f: applet not found
0b748c9fe495:~$
So it looks like we need some way to work around busybox' insistance
that argv[0] determines which applet to run.
With regards,
Daniel
--
|:
https://berrange.com -o-
https://www.flickr.com/photos/dberrange :|
|:
https://libvirt.org -o-
https://fstop138.berrange.com :|
|:
https://entangle-photo.org -o-
https://www.instagram.com/dberrange :|