Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

def-file: Document %post -c <shell>, from sylabs195 #248

Merged
merged 2 commits into from
Mar 8, 2024
Merged

def-file: Document %post -c <shell>, from sylabs195 #248

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
baed11e
def-file: Document %post -c <shell>
dtrudg Aug 31, 2023
ef8c6b4
patch the cherry picked docs
JasonYangShadow Mar 7, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions definition_files.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -393,6 +393,25 @@ container at runtime.
``${ENVPREFIX}_ENVIRONMENT`` take precedence over those added via
``%environment``.

The ``%post`` scriptlet will run under ``sh`` or ``bash`` by default. You can
change the shell or interpreter that the scriptlet runs under by using a ``-c
<shell>`` argument on the ``%post`` line, e.g:

.. code:: {command}

%post -c /bin/zsh
...

In the ``%post`` section above, the scriptlet will be run by the zsh shell
installed at ``/bin/zsh`` in the container. The requested shell must be present
in the base image that was bootstrapped.

.. note::

Unlike the ``%test`` and ``%runscript`` sections, the ``%post`` section does
not support hashbang lines (``#!``) for specifying a custom shell. The ``-c
<shell>`` argument must be used instead.

.. _def-test-section:

%test
Expand Down
Loading