docs: fix typos
This commit is contained in:
parent
e4f701b315
commit
16185dbe05
|
|
@ -25,7 +25,7 @@ for AMD64 machine with the following command:
|
|||
|
||||
.. code-block:: sh
|
||||
|
||||
$ MACHINE=container-x64 bitbake core-image-minimal
|
||||
$ MACHINE=container-x64 bitbake coreos-image-minimal
|
||||
|
||||
|
||||
This will generate a container tarball in the tar.gz format.
|
||||
|
|
@ -57,7 +57,7 @@ To run an interactive shell, you can use:
|
|||
/ #
|
||||
|
||||
The `<IMAGE_ID>` should be copied from the output of `podman import`. In this
|
||||
exemple, it was
|
||||
example, it was
|
||||
`051856498a59e0ae6349492539efaf915a33dd73e7a54ce9683b0414d1481fae`.
|
||||
|
||||
You are now inside the container, try the following command:
|
||||
|
|
@ -75,7 +75,7 @@ You are now inside the container, try the following command:
|
|||
.. note::
|
||||
|
||||
Image generated using any container machines doesn't include the Linux
|
||||
kernel neither many system componant that are usually not used on a container
|
||||
kernel neither many system component that are usually not used on a container
|
||||
like SystemD or udev. This is done inside the machine configuration by
|
||||
settings all the `VIRTUAL_RUNTIME_<component>` to an empty string.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue