Fossil SCM
URL and whitespace fixes to previous.
Commit
9e73519c01ed10c72c104e6c7bf70897bc3ae3e1800f4347295b7521762511c1
Parent
4cb5c03ea1c0260…
1 file changed
+5
-3
+5
-3
| --- www/containers.md | ||
| +++ www/containers.md | ||
| @@ -11,11 +11,11 @@ | ||
| 11 | 11 | |
| 12 | 12 | |
| 13 | 13 | ## 1. Quick Start |
| 14 | 14 | |
| 15 | 15 | Fossil ships a `Dockerfile` at the top of its source tree, |
| 16 | -[here](/file/Dockerfile), which you can build like so: | |
| 16 | +[here][DF], which you can build like so: | |
| 17 | 17 | |
| 18 | 18 | ``` |
| 19 | 19 | $ docker build -t fossil . |
| 20 | 20 | ``` |
| 21 | 21 | |
| @@ -55,10 +55,12 @@ | ||
| 55 | 55 | simply called `fossil`. The unversioned names are more convenient for |
| 56 | 56 | interactive use, while the versioned ones are good for CI/CD type |
| 57 | 57 | applications since they avoid a conflict with past versions; it lets you |
| 58 | 58 | keep old containers around for quick roll-backs while replacing them |
| 59 | 59 | with fresh ones. |
| 60 | + | |
| 61 | +[DF]: /file/Dockerfile | |
| 60 | 62 | |
| 61 | 63 | |
| 62 | 64 | ## 2. <a id="storage"></a>Repository Storage Options |
| 63 | 65 | |
| 64 | 66 | If you want the container to serve an existing repository, there are at |
| @@ -729,16 +731,16 @@ | ||
| 729 | 731 | “`myproject`” within `~/museum/myproject/repo.fossil`, named according |
| 730 | 732 | to the reasons given [above](#repo-inside). We’ll make consistent use of |
| 731 | 733 | this naming scheme in the examples below so that you will be able to |
| 732 | 734 | replace the “`myproject`” element of the various file and path names. |
| 733 | 735 | |
| 734 | -If you use [the stock `Dockerfile`](/file/dockerfile) to generate your | |
| 736 | +If you use [the stock `Dockerfile`][DF] to generate your | |
| 735 | 737 | base image, `nspawn` won’t recognize it as containing an OS unless you |
| 736 | 738 | put a line like this into the first stage: |
| 737 | 739 | |
| 738 | 740 | ``` |
| 739 | -COPY containers/os-release /etc/os-release | |
| 741 | + COPY containers/os-release /etc/os-release | |
| 740 | 742 | ``` |
| 741 | 743 | |
| 742 | 744 | That will let you produce a `systemd` “machine” via the OCI image: |
| 743 | 745 | |
| 744 | 746 | ``` |
| 745 | 747 |
| --- www/containers.md | |
| +++ www/containers.md | |
| @@ -11,11 +11,11 @@ | |
| 11 | |
| 12 | |
| 13 | ## 1. Quick Start |
| 14 | |
| 15 | Fossil ships a `Dockerfile` at the top of its source tree, |
| 16 | [here](/file/Dockerfile), which you can build like so: |
| 17 | |
| 18 | ``` |
| 19 | $ docker build -t fossil . |
| 20 | ``` |
| 21 | |
| @@ -55,10 +55,12 @@ | |
| 55 | simply called `fossil`. The unversioned names are more convenient for |
| 56 | interactive use, while the versioned ones are good for CI/CD type |
| 57 | applications since they avoid a conflict with past versions; it lets you |
| 58 | keep old containers around for quick roll-backs while replacing them |
| 59 | with fresh ones. |
| 60 | |
| 61 | |
| 62 | ## 2. <a id="storage"></a>Repository Storage Options |
| 63 | |
| 64 | If you want the container to serve an existing repository, there are at |
| @@ -729,16 +731,16 @@ | |
| 729 | “`myproject`” within `~/museum/myproject/repo.fossil`, named according |
| 730 | to the reasons given [above](#repo-inside). We’ll make consistent use of |
| 731 | this naming scheme in the examples below so that you will be able to |
| 732 | replace the “`myproject`” element of the various file and path names. |
| 733 | |
| 734 | If you use [the stock `Dockerfile`](/file/dockerfile) to generate your |
| 735 | base image, `nspawn` won’t recognize it as containing an OS unless you |
| 736 | put a line like this into the first stage: |
| 737 | |
| 738 | ``` |
| 739 | COPY containers/os-release /etc/os-release |
| 740 | ``` |
| 741 | |
| 742 | That will let you produce a `systemd` “machine” via the OCI image: |
| 743 | |
| 744 | ``` |
| 745 |
| --- www/containers.md | |
| +++ www/containers.md | |
| @@ -11,11 +11,11 @@ | |
| 11 | |
| 12 | |
| 13 | ## 1. Quick Start |
| 14 | |
| 15 | Fossil ships a `Dockerfile` at the top of its source tree, |
| 16 | [here][DF], which you can build like so: |
| 17 | |
| 18 | ``` |
| 19 | $ docker build -t fossil . |
| 20 | ``` |
| 21 | |
| @@ -55,10 +55,12 @@ | |
| 55 | simply called `fossil`. The unversioned names are more convenient for |
| 56 | interactive use, while the versioned ones are good for CI/CD type |
| 57 | applications since they avoid a conflict with past versions; it lets you |
| 58 | keep old containers around for quick roll-backs while replacing them |
| 59 | with fresh ones. |
| 60 | |
| 61 | [DF]: /file/Dockerfile |
| 62 | |
| 63 | |
| 64 | ## 2. <a id="storage"></a>Repository Storage Options |
| 65 | |
| 66 | If you want the container to serve an existing repository, there are at |
| @@ -729,16 +731,16 @@ | |
| 731 | “`myproject`” within `~/museum/myproject/repo.fossil`, named according |
| 732 | to the reasons given [above](#repo-inside). We’ll make consistent use of |
| 733 | this naming scheme in the examples below so that you will be able to |
| 734 | replace the “`myproject`” element of the various file and path names. |
| 735 | |
| 736 | If you use [the stock `Dockerfile`][DF] to generate your |
| 737 | base image, `nspawn` won’t recognize it as containing an OS unless you |
| 738 | put a line like this into the first stage: |
| 739 | |
| 740 | ``` |
| 741 | COPY containers/os-release /etc/os-release |
| 742 | ``` |
| 743 | |
| 744 | That will let you produce a `systemd` “machine” via the OCI image: |
| 745 | |
| 746 | ``` |
| 747 |