diff --git a/appendix.rst b/appendix.rst index 79476f6..4b0f437 100755 --- a/appendix.rst +++ b/appendix.rst @@ -1111,6 +1111,7 @@ currently residing in the Docker daemon's internal storage: Storing signatures 2019/12/11 14:53:24 info unpack layer: sha256:eb7c47c7f0fd0054242f35366d166e6b041dfb0b89e5f93a82ad3a3206222502 INFO: Creating SIF file... + [=====================================================================] 100 % 0s {Project}> The ``{ENVPREFIX}_DOCKER_HOST`` or ``DOCKER_HOST`` environment variables may be @@ -1162,6 +1163,7 @@ from a docker image stored in a ``docker save`` formatted tar file: Storing signatures 2019/12/11 15:25:09 info unpack layer: sha256:eb7c47c7f0fd0054242f35366d166e6b041dfb0b89e5f93a82ad3a3206222502 INFO: Creating SIF file... + [=====================================================================] 100 % 0s {Project}> Keywords diff --git a/build_a_container.rst b/build_a_container.rst index cff3e97..725d7f2 100755 --- a/build_a_container.rst +++ b/build_a_container.rst @@ -342,6 +342,20 @@ To show help about the options available for selected compressor: $ mksquashfs squashfs-root out.squashfs -comp zstd -Xhelp Non-gzip squashfs compression might not work with some installations. +However, note that by default the {command} command now uses its own +bundled recent version of mksquashfs that should have the maximum +compressors enabled. So you might want to explore the help on that +version, for example by setting its directory early in your PATH like +this: + +.. code:: + + $ PATH=$({command} buildcfg | sed -n 's,^LIBEXECDIR=\(.*\),\1/{command}/bin,p'):$PATH + +Also note that by using non-default compression methods that the +resulting SIF file might not be usable by installations that do not have +the decompression method available. This can be especially true for +older versions of {command}. ``--notest`` ============ diff --git a/definition_files.rst b/definition_files.rst index 840388f..9fdf9db 100755 --- a/definition_files.rst +++ b/definition_files.rst @@ -801,6 +801,7 @@ command. This flag accepts a ``varname=value`` pair, as shown here: 2024/03/08 14:17:24 info unpack layer: sha256:f4bb4e8dca02be491b4f72d2ef2127a64ce49c48d0d9c0a0fcaffa625067679d INFO: Adding runscript INFO: Creating SIF file... + [=====================================================================] 100 % 0s INFO: Build complete: ./my_container.sif $ {command} run ./my_container.sif @@ -825,6 +826,8 @@ the path to that file specified using the ``--build-arg-file`` flag to the 2024/03/08 14:17:24 info unpack layer: sha256:f4bb4e8dca02be491b4f72d2ef2127a64ce49c48d0d9c0a0fcaffa625067679d INFO: Adding runscript INFO: Creating SIF file... + [=====================================================================] + 100 % 0s INFO: Build complete: ./my_container.sif $ {command} run ./my_container.sif @@ -879,6 +882,8 @@ using ``--build-arg`` flags: INFO: Adding environment to container INFO: Adding runscript INFO: Creating SIF file... + [=====================================================================] + 100 % 0s INFO: Build complete: ./my_container.sif $ {command} run ./my_container.sif @@ -917,6 +922,8 @@ path to that file using the ``--build-arg-file`` flag: INFO: Adding environment to container INFO: Adding runscript INFO: Creating SIF file... + [=====================================================================] + 100 % 0s INFO: Build complete: ./my_container.sif $ {command} run ./my_container.sif @@ -952,6 +959,8 @@ Or one can use a combination of both strategies: INFO: Adding environment to container INFO: Adding runscript INFO: Creating SIF file... + [=====================================================================] + 100 % 0s INFO: Build complete: ./my_container.sif $ {command} run ./my_container.sif @@ -986,6 +995,8 @@ last occurrence will take precedence: INFO: Adding environment to container INFO: Adding runscript INFO: Creating SIF file... + [=====================================================================] + 100 % 0s INFO: Build complete: ./my_container.sif $ {command} run ./my_container.sif @@ -1024,6 +1035,8 @@ command line will take precedence: INFO: Adding environment to container INFO: Adding runscript INFO: Creating SIF file... + [=====================================================================] + 100 % 0s INFO: Build complete: ./my_container.sif $ {command} run ./my_container.sif @@ -1090,6 +1103,8 @@ using the ``%arguments`` section, as shown here: 2024/03/08 14:52:53 info unpack layer: sha256:f4bb4e8dca02be491b4f72d2ef2127a64ce49c48d0d9c0a0fcaffa625067679d INFO: Adding runscript INFO: Creating SIF file... + [=====================================================================] + 100 % 0s INFO: Build complete: ./my_container.sif $ {command} run ./my_container.sif diff --git a/docker_and_oci.rst b/docker_and_oci.rst index dcf8ff7..c85f8d1 100755 --- a/docker_and_oci.rst +++ b/docker_and_oci.rst @@ -56,6 +56,8 @@ the container that's called ``sylabsio/lolcow:latest``: 2021/10/04 14:50:21 info unpack layer: sha256:16ec32c2132b43494832a05f2b02f7a822479f8250c173d0ab27b3de78b2f058 2021/10/04 14:50:23 info unpack layer: sha256:5ca731fc36c28789c5ddc3216563e8bfca2ab3ea10347e07554ebba1c953242e INFO: Creating SIF file... + [=====================================================================] + 100 % 0s _____________________________ < Mon Oct 4 14:50:30 CDT 2021 > ----------------------------- @@ -672,6 +674,8 @@ name: Writing manifest to image destination Storing signatures INFO: Creating SIF file... + [=====================================================================] + 100 % 0s INFO: Build complete: lolcow_from_docker_cache.sif The tag name must be included in the URI. Unlike when pulling from a @@ -750,6 +754,8 @@ rather than an object hosted by a service, it uses ``:``, not Writing manifest to image destination Storing signatures INFO: Creating SIF file... + [=====================================================================] + 100 % 0s INFO: Build complete: lolcow_tar.sif .. note:: diff --git a/gpu.rst b/gpu.rst index 32c3bd0..133bebe 100644 --- a/gpu.rst +++ b/gpu.rst @@ -98,6 +98,8 @@ to a SIF before you start working with it: $ {command} pull docker://tensorflow/tensorflow:latest-gpu ... INFO: Creating SIF file... + [=====================================================================] + 100 % 0s INFO: Build complete: tensorflow_latest-gpu.sif Then run the container with GPU support: @@ -457,6 +459,8 @@ to a SIF before you start working with it: $ {command} pull docker://rocm/tensorflow:latest ... INFO: Creating SIF file... + [=====================================================================] + 100 % 0s INFO: Build complete: tensorflow_latest.sif Then run the container with GPU support: diff --git a/oci_runtime.rst b/oci_runtime.rst index 1c433a3..30e1b9e 100644 --- a/oci_runtime.rst +++ b/oci_runtime.rst @@ -79,6 +79,8 @@ exists locally. (Recall: Writing manifest to image destination Storing signatures INFO: Creating SIF file... + [=====================================================================] + 100 % 0s INFO: Build complete: busybox_latest.sif This is one way to bootstrap creation of this image in SIF that diff --git a/registry.rst b/registry.rst index 49f21ac..50d239b 100644 --- a/registry.rst +++ b/registry.rst @@ -133,6 +133,8 @@ by passing them the same ``--authfile `` flag: Writing manifest to image destination 2023/09/28 13:15:46 info unpack layer: sha256:7264a8db6415046d36d16ba98b79778e18accee6ffa71850405994cffa9be7de INFO: Creating SIF file... + [=====================================================================] + 100 % 0s Apptainer> .. note:: @@ -182,4 +184,4 @@ both for the ``registry login`` / ``registry logout`` commands and for the `pull `__, `instance `__. -set of commands. \ No newline at end of file +set of commands.