Fossil SCM
Small fix to previous
Commit
d5695c8ef131ac3391c1985a096270de7143c216ca5f4661db7839493dea8d7d
Parent
f9f13ce7a9637a3…
1 file changed
+3
-2
+3
-2
| --- www/containers.md | ||
| +++ www/containers.md | ||
| @@ -686,13 +686,13 @@ | ||
| 686 | 686 | #### <a id="crun"></a>`crun` |
| 687 | 687 | |
| 688 | 688 | In the same way that [Docker Engine is based on `runc`](#runc), Podman’s |
| 689 | 689 | engine is based on [`crun`][crun], a lighter-weight alternative to |
| 690 | 690 | `runc`. It’s only 1.4 MiB on the system I tested it on, yet it will run |
| 691 | +the same container bundles as in my `runc` examples above. | |
| 691 | 692 | Above, we saved more than that by compressing the container’s Fossil |
| 692 | -executable with UPX! the same container bundles as in my `runc` | |
| 693 | -examples above. | |
| 693 | +executable with UPX! | |
| 694 | 694 | |
| 695 | 695 | This makes `crun` a great option for tiny remote hosts with a single |
| 696 | 696 | container, or at least where none of the containers share base layers, |
| 697 | 697 | so that there is no effective cost to duplicating the immutable base |
| 698 | 698 | layers of the containers’ source images. |
| @@ -699,7 +699,8 @@ | ||
| 699 | 699 | |
| 700 | 700 | This suggests one method around the problem of rootless Podman containers: |
| 701 | 701 | `sudo crun`, following the examples above. |
| 702 | 702 | |
| 703 | 703 | [crun]: https://github.com/containers/crun |
| 704 | + | |
| 704 | 705 | |
| 705 | 706 | <div style="height:50em" id="this-space-intentionally-left-blank"></div> |
| 706 | 707 |
| --- www/containers.md | |
| +++ www/containers.md | |
| @@ -686,13 +686,13 @@ | |
| 686 | #### <a id="crun"></a>`crun` |
| 687 | |
| 688 | In the same way that [Docker Engine is based on `runc`](#runc), Podman’s |
| 689 | engine is based on [`crun`][crun], a lighter-weight alternative to |
| 690 | `runc`. It’s only 1.4 MiB on the system I tested it on, yet it will run |
| 691 | Above, we saved more than that by compressing the container’s Fossil |
| 692 | executable with UPX! the same container bundles as in my `runc` |
| 693 | examples above. |
| 694 | |
| 695 | This makes `crun` a great option for tiny remote hosts with a single |
| 696 | container, or at least where none of the containers share base layers, |
| 697 | so that there is no effective cost to duplicating the immutable base |
| 698 | layers of the containers’ source images. |
| @@ -699,7 +699,8 @@ | |
| 699 | |
| 700 | This suggests one method around the problem of rootless Podman containers: |
| 701 | `sudo crun`, following the examples above. |
| 702 | |
| 703 | [crun]: https://github.com/containers/crun |
| 704 | |
| 705 | <div style="height:50em" id="this-space-intentionally-left-blank"></div> |
| 706 |
| --- www/containers.md | |
| +++ www/containers.md | |
| @@ -686,13 +686,13 @@ | |
| 686 | #### <a id="crun"></a>`crun` |
| 687 | |
| 688 | In the same way that [Docker Engine is based on `runc`](#runc), Podman’s |
| 689 | engine is based on [`crun`][crun], a lighter-weight alternative to |
| 690 | `runc`. It’s only 1.4 MiB on the system I tested it on, yet it will run |
| 691 | the same container bundles as in my `runc` examples above. |
| 692 | Above, we saved more than that by compressing the container’s Fossil |
| 693 | executable with UPX! |
| 694 | |
| 695 | This makes `crun` a great option for tiny remote hosts with a single |
| 696 | container, or at least where none of the containers share base layers, |
| 697 | so that there is no effective cost to duplicating the immutable base |
| 698 | layers of the containers’ source images. |
| @@ -699,7 +699,8 @@ | |
| 699 | |
| 700 | This suggests one method around the problem of rootless Podman containers: |
| 701 | `sudo crun`, following the examples above. |
| 702 | |
| 703 | [crun]: https://github.com/containers/crun |
| 704 | |
| 705 | |
| 706 | <div style="height:50em" id="this-space-intentionally-left-blank"></div> |
| 707 |