Skip to content

Update using-containers-in-the-tre.md - added Container image management #196

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update using-containers-in-the-tre.md - added Container image management #196

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
15 changes: 14 additions & 1 deletion docs/safe-haven-services/tre-container-user-guide/using-containers-in-the-tre.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,20 @@ To pull a public image, which does not require authenticating with username and
ces-pull "" "" ghcr.io/<namespace>/<container_name>[:<container_tag>]
```

Once the container image has been pulled into the TRE desktop host, the image can be managed with Podman commands. However, containers must not be run directly using Podman. Instead, commands developed for use within the TRE must be used as will now be described.
Once the container image has been pulled into the TRE desktop host, the image can be managed with Podman commands. However, containers must not be run directly using Podman. Instead, commands developed for use within the TRE must be used as described below.

## Container image management

Container images can be listed:
```
$ podman images
REPOSITORY TAG IMAGE ID CREATED SIZE
ghcr.io/github_user/container_name latest a9993c28f847 5 days ago 622 MB
tre-ghcr-proxy.nsh.loc:5005/github_user/container_name latest a9993c28f847 5 days ago 622 MB
```
Notice that two entries are shown; they are the same image as they have identical `IMAGE ID`.
Images that are no longer required should be removed with `podman rmi -f IMAGE_ID`
followed by `podman image prune`.

## Running the container in the TRE

Expand Down