From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH 2/2] doc: add isar build in docker instructions
Date: Mon, 23 Apr 2018 09:12:47 +0200 [thread overview]
Message-ID: <44fed440-401c-1b76-8f84-42102c62591e@siemens.com> (raw)
In-Reply-To: <20180420095555.21357-3-mosipov@ilbers.de>
On 2018-04-20 11:55, Maxim Yu. Osipov wrote:
> Signed-off-by: Maxim Yu. Osipov <mosipov@ilbers.de>
> ---
> doc/docker_build.md | 46 ++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 46 insertions(+)
> create mode 100644 doc/docker_build.md
>
> diff --git a/doc/docker_build.md b/doc/docker_build.md
> new file mode 100644
> index 0000000..7471f2d
> --- /dev/null
> +++ b/doc/docker_build.md
> @@ -0,0 +1,46 @@
> +# Building ISAR in Docker
> +
> +ISAR docker's images are public.
> +
> +## Install Docker
> +
> +Follow the instructions on https://docs.docker.com/install
> +
> +## Build ISAR in Docker
> +
> +Try the following command on your Linux host running docker:
> +
> +```
> +$docker run -e USER_ID=$(id -u) --rm -t -i --cap-add=SYS_ADMIN --device $(/sbin/losetup -f) kasproject/kas-isar bash
Did you validate that we no longer need --cap-add=MKNOD?
We definitely need --privileged when doing cross-builds in order to set
up binfmt if the host is not using it.
Here is a working reference for native as well as cross-setup:
https://github.com/siemens/jailhouse-images/blob/master/build-images.sh
It also demonstrates how to avoid that interactive mode (which is what
you normally want when you aren't developing on details). Plus, it
addresses the proxy topic.
Jan
> +```
> +
> +You will see someting like:
> +
> +```
> +Unable to find image 'kasproject/kas-isar:latest' locally
> +latest: Pulling from kasproject/kas-isar
> +b0568b191983: Pull complete
> +4275668792f8: Pull complete
> +f20834504b2f: Pull complete
> +8fc4f86edf96: Pull complete
> +abfe5b5ad18a: Pull complete
> +a903a3cbb4d5: Pull complete
> +2bd66d0e3147: Pull complete
> +cdd19e96269b: Pull complete
> +fbb3475f667d: Pull complete
> +89116d7487d0: Pull complete
> +Digest: sha256:7cfee2a6ac9a197e9d1bead0091854f2a53ca90a12453d21264dba525670fba5
> +Status: Downloaded newer image for kasproject/kas-isar:latest
> +builder@ce7cfc1d57db:~$
> +```
> +
> +Clone the isar repository and launch build for target isar image name:
> +
> +```
> +builder@ce7cfc1d57db:~$ git clone https://github.com/ilbers/isar.git
> +
> +builder@ce7cfc1d57db:~$ cd isar/
> +
> +builder@ce7cfc1d57db:~/isar$ . ./isar-init-build-env ../build
> +builder@ce7cfc1d57db:~/build$ bitbake <isar-image-name>
> +```
>
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2018-04-23 7:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 9:55 [PATCH 0/2] Various doc updates Maxim Yu. Osipov
2018-04-20 9:55 ` [PATCH 1/2] doc: add supported host distro section Maxim Yu. Osipov
2018-04-20 9:55 ` [PATCH 2/2] doc: add isar build in docker instructions Maxim Yu. Osipov
2018-04-23 7:12 ` Jan Kiszka [this message]
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=44fed440-401c-1b76-8f84-42102c62591e@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=mosipov@ilbers.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