public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH v2 1/1] Dockerfile: provide kernel for libguestfs-tools
Date: Tue, 14 Jul 2020 17:28:21 -0400	[thread overview]
Message-ID: <20200714212821.GP6227@bill-the-cat> (raw)
In-Reply-To: <20200714061856.4487-1-xypron.glpk@gmx.de>

On Tue, Jul 14, 2020 at 08:18:56AM +0200, Heinrich Schuchardt wrote:

> The libguestfs-tools use QEMU to mount an image file. This requires a Linux
> kernel.
> 
> On Ubuntu the kernel (/boot/vmlinuz*) is not readable for normal users
> (chmod 600), cf.
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759725
> 
> Install a kernel and make it readable for all users (chmod 644).
> 
> Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>

This causes the tests to fail now that they're trying to use
libguestfs-tools:
https://gitlab.denx.de/u-boot/u-boot/-/jobs/124872

I did a quick change to pass in the KVM group to useradd as well, but
that didn't catch.  I suspect that changing /dev/kvm inside the
container won't stick either.  But that shouldn't be fatal as it's still
fast enough.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200714/bd1125fc/attachment.sig>

  reply	other threads:[~2020-07-14 21:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-14  6:18 [PATCH v2 1/1] Dockerfile: provide kernel for libguestfs-tools Heinrich Schuchardt
2020-07-14 21:28 ` Tom Rini [this message]
2020-07-14 22:00   ` Heinrich Schuchardt
2020-07-14 22:10     ` Tom Rini
2020-07-20  6:26       ` Heinrich Schuchardt
2020-07-20 12:32         ` Tom Rini

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=20200714212821.GP6227@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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