Fossil SCM
Fixed a problem in image naming in the new Docker container doc in build.wiki [forum:/forumpost/2fd50423377d0f51 | reported on the forum].
Commit
509447a2d7cf4181b186d0a341678e5c81b7a71bcb15a3e10e126293e939fe50
Parent
289c9b501cb724a…
1 file changed
+5
-5
+5
-5
| --- www/build.wiki | ||
| +++ www/build.wiki | ||
| @@ -313,16 +313,16 @@ | ||
| 313 | 313 | A secondary benefit falls out of this process for free: it's arguably |
| 314 | 314 | the easiest way to build a purely static Fossil binary for Linux. Most |
| 315 | 315 | modern Linux distros make this surprisingly difficult, but Alpine's |
| 316 | 316 | back-to-basics nature makes static builds work the way they used to, |
| 317 | 317 | back in the day. If that's what you're after, you can skip the "run" |
| 318 | -command above and extract the executable from the image instead: | |
| 318 | +command above and create a tmporary container from the image, then | |
| 319 | +extract the executable from it instead: | |
| 319 | 320 | |
| 320 | -<pre><code> $ docker create --name fossil_static fossil_static | |
| 321 | - $ docker cp fossil_static:/jail/bin/fossil . | |
| 322 | - $ docker container rm fossil_static | |
| 323 | - $ docker image rm fossil_static | |
| 321 | +<pre><code> $ docker create --name fossil-static-tmp fossil | |
| 322 | + $ docker cp fossil-static-tmp:/jail/bin/fossil . | |
| 323 | + $ docker container rm fossil-static-tmp | |
| 324 | 324 | </code></pre> |
| 325 | 325 | |
| 326 | 326 | The resulting binary is the single largest file inside that container, |
| 327 | 327 | at about 6 MiB. (It's built stripped.) |
| 328 | 328 | |
| 329 | 329 |
| --- www/build.wiki | |
| +++ www/build.wiki | |
| @@ -313,16 +313,16 @@ | |
| 313 | A secondary benefit falls out of this process for free: it's arguably |
| 314 | the easiest way to build a purely static Fossil binary for Linux. Most |
| 315 | modern Linux distros make this surprisingly difficult, but Alpine's |
| 316 | back-to-basics nature makes static builds work the way they used to, |
| 317 | back in the day. If that's what you're after, you can skip the "run" |
| 318 | command above and extract the executable from the image instead: |
| 319 | |
| 320 | <pre><code> $ docker create --name fossil_static fossil_static |
| 321 | $ docker cp fossil_static:/jail/bin/fossil . |
| 322 | $ docker container rm fossil_static |
| 323 | $ docker image rm fossil_static |
| 324 | </code></pre> |
| 325 | |
| 326 | The resulting binary is the single largest file inside that container, |
| 327 | at about 6 MiB. (It's built stripped.) |
| 328 | |
| 329 |
| --- www/build.wiki | |
| +++ www/build.wiki | |
| @@ -313,16 +313,16 @@ | |
| 313 | A secondary benefit falls out of this process for free: it's arguably |
| 314 | the easiest way to build a purely static Fossil binary for Linux. Most |
| 315 | modern Linux distros make this surprisingly difficult, but Alpine's |
| 316 | back-to-basics nature makes static builds work the way they used to, |
| 317 | back in the day. If that's what you're after, you can skip the "run" |
| 318 | command above and create a tmporary container from the image, then |
| 319 | extract the executable from it instead: |
| 320 | |
| 321 | <pre><code> $ docker create --name fossil-static-tmp fossil |
| 322 | $ docker cp fossil-static-tmp:/jail/bin/fossil . |
| 323 | $ docker container rm fossil-static-tmp |
| 324 | </code></pre> |
| 325 | |
| 326 | The resulting binary is the single largest file inside that container, |
| 327 | at about 6 MiB. (It's built stripped.) |
| 328 | |
| 329 |