Fossil

Diff
Login

Diff

Differences From Artifact [0bd3fa413a]:

To Artifact [901a4a2dfb]:


738
739
740
741
742
743
744

745
746
747
748

749
750
751



752
753
754
755
756
757
758
“`myproject`” within `~/museum/myproject/repo.fossil`, named according
to the reasons given [above](#repo-inside). We’ll make consistent use of
this naming scheme in the examples below so that you will be able to
replace the “`myproject`” element of the various file and path names.

If you use [the stock `Dockerfile`][DF] to generate your
base image, `nspawn` won’t recognize it as containing an OS unless you

put a line like this into the first stage:

```
  COPY containers/os-release /etc/os-release

```

That will let you produce a `systemd` “machine” via the OCI image:




```
  $ make container
  $ docker container export $(make container-version) |
    machinectl import-tar - myproject
```








>
|


<
>


<
>
>
>







738
739
740
741
742
743
744
745
746
747
748

749
750
751

752
753
754
755
756
757
758
759
760
761
“`myproject`” within `~/museum/myproject/repo.fossil`, named according
to the reasons given [above](#repo-inside). We’ll make consistent use of
this naming scheme in the examples below so that you will be able to
replace the “`myproject`” element of the various file and path names.

If you use [the stock `Dockerfile`][DF] to generate your
base image, `nspawn` won’t recognize it as containing an OS unless you
change the “`FROM scratch AS os`” line at the top of the second stage
to something like this:

```

  FROM gcr.io/distroless/static-debian11 AS os
```


Using that as a base image provides all the files `nspawn` checks for to
determine whether the container is sufficiently close to a Linux VM for
the following step to proceed:

```
  $ make container
  $ docker container export $(make container-version) |
    machinectl import-tar - myproject
```