From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2018-10-26
Date: Sat, 27 Oct 2018 15:28:24 +0200 [thread overview]
Message-ID: <20181027152824.2160f61d@windsurf> (raw)
In-Reply-To: <CANQCQpbXOhEgYe_kCqKfEnQMLGrsRh7knZARrxdn3P9qdjf_1w@mail.gmail.com>
Hello,
On Sat, 27 Oct 2018 07:26:23 -0500, Matthew Weber wrote:
> This was a sandboxed failure. The sandbox was setup by using
> bubblewrap with the options below. It stages an OS environment where
> the "--dir" items are new empty write-able directories and the
> ro-binds are readonly bind mounts of that file or location to the new
> location inside the sandbox. The user/group is also stripped to just
> the minimal root, calling user and 65534. Right now the whole
> autobuilder-run script is being executed inside a single sandbox and
> there is no checking for new files in the write-able empty folders.
> --ro-bind /bin /bin \
> --ro-bind /etc/resolv.conf /etc/resolv.conf \
> --ro-bind /etc/profile /etc/profile \
> --ro-bind /etc/environment /etc/environment \
> --ro-bind /etc/alternatives /etc/alternatives \
> --ro-bind /etc/ld.so.conf /etc/ld.so.conf \
> --ro-bind /etc/ld.so.cache /etc/ld.so.cache \
> --ro-bind /etc/ld.so.conf.d /etc/ld.so.conf.d \
> --ro-bind /etc/xml /etc/xml \
> --ro-bind /etc/sgml /etc/sgml \
> --ro-bind /lib /lib \
> --ro-bind /lib32 /lib32 \
> --ro-bind /libx32 /libx32 \
> --ro-bind /lib64 /lib64 \
> --ro-bind /sbin /sbin \
> --ro-bind /usr /usr \
> --dir /home \
> --dir /home/bruser \
> --bind /home/bruser/buildroot-test /home/bruser/buildroot-test \
> --dir /tmp \
> --dir /var \
> --dir /run \
> --symlink ../tmp var/tmp \
> --symlink ../run var/run \
> --proc /proc \
> --dev /dev \
> --chdir / \
> --unshare-all \
> --share-net \
> --die-with-parent \
> --dir /run/user/$(id -u) \
> --setenv XDG_RUNTIME_DIR "/run/user/`id -u`" \
> --setenv PS1 "bwrap-demo$ " \
> --file 11 /etc/passwd \
> --file 12 /etc/group \
> /bin/bash) \
> 11< <(getent passwd 0 $UID 65534) \
> 12< <(getent group 0 $(id -g) 65534) \
Thanks. Should we add support for this directly in autobuild-run ?
> For this failure, it uncovered Xmlto validation was using the host
> OS's docbook dtd's. I've mapped the /etc/xml and /etc/sgml into the
> sandbox to resolve this failure. I assume for something like this an
> update to have it use a Buildroot host tool isn't necessary as the
> xmlto they are using isn't built as a dependency?
This has been resolved by commit
https://git.buildroot.org/buildroot/commit/?id=220f25e9407a17804719d5355196f50b2d5e1f55
> > gpsd-3.18 | 5
>
> Same failure as giflib.
>
> > openswan-2.6.50 | 1
>
>
> Same failure as giflib.
Those two need investigation.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-10-27 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-27 6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-10-26 Thomas Petazzoni
2018-10-27 12:26 ` Matthew Weber
2018-10-27 13:28 ` Thomas Petazzoni [this message]
2018-10-29 13:10 ` Matthew Weber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181027152824.2160f61d@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox