You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
adding support to install from local container (#602)
* adding support to install from local container
* add --keep-path to not relocate container
this means that a user can select a registry entry
(container.yaml) to use for metadata, and apply to
a local container. This still requires choice of
an explicit registry entry for metadata selection.
Signed-off-by: vsoch <[email protected]>
Copy file name to clipboardExpand all lines: docs/getting_started/user-guide.rst
+34Lines changed: 34 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1158,13 +1158,47 @@ the container technology.
1158
1158
If you don't have any module software on your system, you can now test interacting
1159
1159
with the module via the :ref:`getting_started-development` instructions.
1160
1160
1161
+
.. _getting_started-commands-install-private:
1162
+
1161
1163
1162
1164
Install Private Images
1163
1165
----------------------
1164
1166
1165
1167
What about private containers on Docker Hub? If you have a private image, you can
1166
1168
simply use `Singularity remote login <https://github.com/sylabs/singularity-userdocs/blob/master/singularity_and_docker.rst#singularity-cli-remote-command>`_ before attempting the install and everything should work.
1167
1169
1170
+
.. _getting_started-commands-install-local:
1171
+
1172
+
1173
+
Install Local Image
1174
+
-------------------
1175
+
1176
+
The concept of installing a local image means that you are selecting a container.yaml recipe from an existing registry,
1177
+
however instead of pulling it, you are pairing it was a particular URI of a local image. As an example, let's say we have pulled a local
0 commit comments