From: Ben Hutchings <ben.hutchings@codethink.co.uk>
To: daniel.sangorrin@toshiba.co.jp, jan.kiszka@siemens.com
Cc: isar-users@googlegroups.com, cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] isar error log
Date: Wed, 03 Apr 2019 14:53:11 +0100 [thread overview]
Message-ID: <1554299591.3557.13.camel@codethink.co.uk> (raw)
In-Reply-To: <OSAPR01MB37634FC9265275C1F909D27AD0570@OSAPR01MB3763.jpnprd01.prod.outlook.com>
On Wed, 2019-04-03 at 00:56 +0000, daniel.sangorrin@toshiba.co.jp wrote:
> Hi Jan,
>
> Yes I am following the Readme.
>
> The docker image id for kasproject/kas-isar is 9e9fe44e68d3 (I am using kas-docker script). And I am using
> kas-docker --isar build kas.yml:board-qemu-amd64.yml
>
> Yes, it seems there are multiple errors:
> /proc/sys/fs/binfmt_misc/register: Invalid argument
> /test-dev-null: Permission denied
>
> Probably this is a bug or misconfiguration in Ubuntu. I will try to figure it out.
Might this be restricted by an AppArmor profile? aa-logprof should
show you AppArmor denials and change the relevant profile(s) to allow
the operations.
Ben.
--
Ben Hutchings, Software Developer Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
Manchester, M1 2HF, United Kingdom
next prev parent reply other threads:[~2019-04-03 13:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 3:17 daniel.sangorrin
2019-04-02 6:13 ` Jan Kiszka
2019-04-03 0:56 ` daniel.sangorrin
2019-04-03 5:55 ` Jan Kiszka
2019-04-11 9:08 ` daniel.sangorrin
2019-04-11 9:15 ` Jan Kiszka
2019-04-11 10:05 ` daniel.sangorrin
2019-04-11 10:13 ` daniel.sangorrin
2019-04-11 12:42 ` Jan Kiszka
2019-04-12 11:37 ` Henning Schild
2019-04-12 11:59 ` [cip-dev] " Ben Hutchings
2019-04-16 2:47 ` daniel.sangorrin
2019-04-16 3:04 ` daniel.sangorrin
2019-04-03 13:53 ` Ben Hutchings [this message]
2019-04-05 7:44 ` daniel.sangorrin
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=1554299591.3557.13.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--cc=cip-dev@lists.cip-project.org \
--cc=daniel.sangorrin@toshiba.co.jp \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
/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