|
1 | 1 | .. _whats_new:
|
2 | 2 |
|
3 | 3 | ###############################
|
4 |
| -What's New in {Singularity} 4.2 |
| 4 | +What's New in {Singularity} 4.3 |
5 | 5 | ###############################
|
6 | 6 |
|
7 |
| -This section highlights important changes and new features in {Singularity} 4.2 |
| 7 | +This section highlights important changes and new features in {Singularity} 4.3 |
8 | 8 | that are of note to users. See also the "What's New" section in the Admin Guide
|
9 | 9 | for administrator-facing changes.
|
10 |
| - |
11 |
| -If you are upgrading from a 3.x version of {Singularity} we recommend also |
12 |
| -reviewing the `"What's New" section for 4.0 |
13 |
| -<https://docs.sylabs.io/guides/4.0/user-guide/new.html>`__. |
14 |
| - |
15 |
| -******** |
16 |
| -OCI-mode |
17 |
| -******** |
18 |
| - |
19 |
| -- A new ``--layer-format tar`` flag for ``singularity push`` allows layers in an |
20 |
| - OCI-SIF image to be pushed to ``library://`` and ``docker://`` registries with |
21 |
| - layers in the standard OCI tar format. Images pushed with ``--layer-format`` |
22 |
| - tar can be pulled and run by other OCI runtimes. See :ref:`sec:layer-format`. |
23 |
| - |
24 |
| -- Persistent overlays embedded in OCI-SIF files. See :ref:`overlay-oci-sif`. |
25 |
| - |
26 |
| - - A writable overlay can be added to an OCI-SIF file with the ``singularity |
27 |
| - overlay create`` command. The overlay will be applied read-only, by default, |
28 |
| - when executing the OCI-SIF. To write changes to the container into the |
29 |
| - overlay, use the ``--writable`` flag. |
30 |
| - - A writable overlay is added to an OCI-SIF file as an ext3 format layer, |
31 |
| - appended to the encapsulated OCI image. After the overlay has been modified, |
32 |
| - use the ``singularity overlay sync`` command to synchronize the OCI digests with |
33 |
| - the overlay content. |
34 |
| - - A new ``singularity overlay seal`` command converts a writable overlay inside |
35 |
| - an OCI-SIF image into a read-only squashfs layer. This seals changes made to |
36 |
| - the image via the overlay, so that they are permanent. |
37 |
| - |
38 |
| -- OCI-SIF data containers provide a way to package reference data into an |
39 |
| - OCI-SIF file that can be distributed alongside application containers. See |
40 |
| - :ref:`sec:data-containers`. |
41 |
| - |
42 |
| - - A new ``singularity data package`` command allows files and directories to |
43 |
| - be packaged into an OCI-SIF data container. |
44 |
| - - A new ``--data <data container>:<dest>`` flag for OCI-Mode allows the |
45 |
| - contents of a data container to be made available at ``<dest>`` inside an |
46 |
| - application container. |
47 |
| - |
48 |
| - |
49 |
| -******* |
50 |
| -Runtime |
51 |
| -******* |
52 |
| - |
53 |
| -- The new ``--netns-path`` flag takes a path to a network namespace to join when |
54 |
| - starting a container. The root user may join any network namespace. An |
55 |
| - unprivileged user can only join a network namespace specified in the new |
56 |
| - allowed ``netns paths directive`` in ``singularity.conf``, if they are also |
57 |
| - listed in ``allow net users`` / ``allow net groups``. Not currently supported |
58 |
| - with ``--fakeroot``, or in ``--oci`` mode. See :ref:`sec:netns-path`. |
59 |
| -- Instances can now be started via the new subcommand ``singularity instance |
60 |
| - run``, which will cause the instance to execute its ``%runscript`` rather than |
61 |
| - the ``%startscript``. |
62 |
| - |
0 commit comments