727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
|
We’ll assume your Fossil repository stores something called
“`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.
The first configuration step is to convert the Docker container into
a “machine,” as `systemd` calls it. The easiest method is:
Next, create `/etc/systemd/nspawn/myproject.nspawn`, containing
something like:
----
```
[Exec]
WorkingDirectory=/jail
Parameters=bin/fossil server \
|
>
>
>
|
>
>
>
|
>
|
<
|
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
|
We’ll assume your Fossil repository stores something called
“`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`](/file/dockerfile) 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
```
Next, create `/etc/systemd/nspawn/myproject.nspawn`:
----
```
[Exec]
WorkingDirectory=/jail
Parameters=bin/fossil server \
|