public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Cc: "Cirujano-Cuesta, Silvano" <silvano.cirujano-cuesta@siemens.com>
Subject: [PATCH] doc: Fix and simplify container image loading description
Date: Sun, 9 May 2021 10:02:26 +0200	[thread overview]
Message-ID: <d334a077-dea8-e571-1244-876cb457041a@siemens.com> (raw)

From: Jan Kiszka <jan.kiszka@siemens.com>

The manual was incorrectly referencing 'docker import', rather than what
was also used in the example: only 'docker load' works for the generated
images.

And the proposed command line can be simplified by passing the image
directly to 'docker load'.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
 doc/user_manual.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/user_manual.md b/doc/user_manual.md
index 2749ef0..2f7df87 100644
--- a/doc/user_manual.md
+++ b/doc/user_manual.md
@@ -258,7 +258,7 @@ Container images can be generated in different formats, selected with the
 variable `CONTAINER_FORMAT`. One or more (whitespace separated) of following 
 options can be given:
  - `docker-archive`: (default) an archive containing a Docker image that can 
-   be imported with [`docker import`](https://docs.docker.com/engine/reference/commandline/import/)
+   be imported with [`docker load`](https://docs.docker.com/engine/reference/commandline/load)
  - `docker-daemon`: resulting container image is made available on the local 
    Docker Daemon
  - `containers-storage`: resulting container image is made available to tools 
@@ -300,7 +300,7 @@ bitbake mc:qemuarm-buster:isar-image-base
  - Load the container image into the Docker Daemon
 
 ```
-xzcat build/tmp/deploy/images/qemuarm/debian-buster-armhf-docker-archive.tar.xz | docker load
+docker load -i build/tmp/deploy/images/qemuarm/debian-buster-armhf-docker-archive.tar.xz
 ```
 
  - Run a container using the container image (following commands starting with 
@@ -1019,7 +1019,7 @@ Supported formats are:
    "[Create an ISAR SDK root filesystem](#create-an-isar-sdk-root-filesystem)"
  - `docker-archive`: an archive containing a Docker image that can be imported 
    with 
-   [`docker import`](https://docs.docker.com/engine/reference/commandline/import/)
+   [`docker load`](https://docs.docker.com/engine/reference/commandline/load)
  - `docker-daemon`: resulting container image is made available on the local 
    Docker Daemon
  - `containers-storage`: resulting container image is made available to tools 
@@ -1071,7 +1071,7 @@ bitbake -c do_populate_sdk mc:qemuarm-buster:isar-image-base
  - Load the SDK container image into the Docker Daemon
 
 ```
-xzcat build/tmp/deploy/images/qemuarm/sdk-debian-buster-armhf-docker-archive.tar.xz | docker load
+docker load -i build/tmp/deploy/images/qemuarm/sdk-debian-buster-armhf-docker-archive.tar.xz
 ```
 
  - Run a container using the SDK container image (following commands starting 
-- 
2.26.2

             reply	other threads:[~2021-05-09  8:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-09  8:02 Jan Kiszka [this message]
2021-06-08  6:47 ` Anton Mikanovich

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=d334a077-dea8-e571-1244-876cb457041a@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=silvano.cirujano-cuesta@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