Procedure

1. Log in to your local automation hub.
2. Navigate to User Access → Groups.
3. Click Create.
4. Provide a Name and click Create.

Procedure

1. Log in to your local automation hub.
2. Navigate to User Access → Roles.
3. Click Add roles.
4. Click in the name field and fill in the role name.
5. Click in the description field and fill in the description.
6. Complete the Permissions section.
7. Click in the field for each permission type and select permissions that appear in the list.
8. Click Save when finished assigning permissions.
9. Navigate to User Access → Groups.
10. Click on a group name.
11. Click on the Access tab.
12. Click Add roles.
13. Select the role created in step 8.
14. Click Next to confirm the selected role.
15. Click Add to complete adding the role.

Procedure

1. Log in to automation hub.
2. Navigate to User Access → Groups.
3. Click on a Group name.
4. Navigate to the Users tab, then click Add.
5. Select users to add from the list and click Add.

Procedure

1. Log in to Podman using your registry.redhat.io credentials:

   $ podman login registry.redhat.io

2. Enter your username and password at the prompts.

3. Pull a container image:

   $ podman pull registry.redhat.io/<container_image_name>:<tag>

Verification

1. List the images in local storage:

   $ podman images

2. Verify that the image you recently pulled is contained in the list.
3. Verify that the tag is correct.

Verification

1. List the images in local storage:

   $ podman images

2. Verify that the image you recently tagged with your automation hub information is contained in the list.

Procedure

1. Log in to Podman using your automation hub location and credentials:

   $ podman login -u=<username> -p=<password> <automation_hub_url>

2. Push your container image to your automation hub container registry:

   $ podman push <automation_hub_url>/<container_image_name>

   Note

   The --remove-signatures flag is required when signed images from registry.redhat.io are pushed to the automation hub container registry. The push operation re-compresses image layers during the upload, which is not guaranteed to be reproducible and is client implementation dependent. This may lead to image-layer digest changes and a failed push operation, resulting in Error: Copying this image requires changing layer representation, which is not possible (image is signed or the destination specifies a digest).

Verification

1. Log in to your automation hub.
2. Navigate to Container Registry.
3. Locate the container in the container repository list.

Procedure

1. Navigate to Execution Environments.
2. Select your container repository.
3. On the Detail tab, click Add.
4. In the Raw Markdown text field, enter your README text in Markdown.
5. Click Save when you are finished.

Procedure

1. Navigate to Execution Environments.
2. Select your container repository.
3. Click Edit at the top right of your window.

4. Under Groups with access, select a group or groups to grant access to.

   • Optional: Add or remove permissions for a specific group using the drop down under that group name.
5. Click Save.

Procedure

1. Navigate to Execution Environments.
2. Select your container repository.
3. Click the Images tab.
4. Click the More Actions icon ⋮, then click Manage tags.

5. Add a new tag in the text field and click Add.

   • Optional: Remove current tags by clicking x on any of the tags for that image.
6. Click Save.

Procedure

1. Navigate to automation controller.
2. In the side-menu bar, click Resources → Credentials.
3. Click Add to create a new credential.
4. Enter an authorization Name, Description, and Organization.
5. Select the Credential Type.
6. Enter the Authentication URL. This is the container registry address.
7. Enter the Username and Password or Token required to log in to the container registry.
8. Optionally, select Verify SSL to enable SSL verification.
9. Click Save.

Procedure

1. Navigate to Execution Environments.
2. Select your container repository.
3. In the Pull this image entry, click Copy to clipboard.
4. Paste and run the command in your terminal.

1. Navigate to Execution Environments → Remote Registries.
2. Add https://registry.redhat.io to the registry.
3. Add any required credentials to authenticate.

1. Navigate to Execution Environments → Execution Environments.
2. Click Add execution environment in the page header.
3. Select the registry you wish to pull from. The "name" field displays the name of the image that will show up as on your local registry.

Procedure

1. Deploy your system with support for container signing activated.

   _automation_hub:
       automationhub_create_default_container_signing_service: true
       automationhub_container_signing_service_key: _path/to/gpg.key_
       automationhub_container_signing_service_script: _path/to/executable_

2. Navigate to automation hub.
3. In the navigation pane, select Signature Keys.
4. Ensure you have a key titled container-default, or container-anyname.

1. In automation hub, click Execution Environments in the main menu pane. Two choices become available, Execution Environments, and Remote Registries.
2. Click Remote Registries.

3. Click Add Remote Registry in the main window.

   • In the Name field, enter the name of the registry where the container resides.
   • In the URL field, enter the URL of the registry where the container resides.
   • In the Username field, enter the username if necessary.
   • In the Password field, enter the password if necessary.
   • Click Save.

Procedure

1. Navigate to Execution Environments.
2. Enter the name of the execution environment.
3. Optional: Enter the upstream name.
4. Under the Registry, select the name of the registry from the drop-down menu.
5. Enter tags in the Add tags to include field. If the field is left blank, all of the tags will be passed. So it is important to pass repository specific tags.

6. The remaining fields are optional:

   • Currently included tags
   • Add tag(s) to exclude
   • Currently excluded tag(s)
   • Description
   • Groups with access
7. Click Save.
8. Synchronize the image.

Procedure

1. From a terminal, log into podman, or any container client currently in use.

   > podman pull <__container-name__>

2. After the image is pulled, add tags:

   > podman tag <container-name> _<server-address>_/<container-name>:<tag name>

3. Sign the image after changes have been made, and push it back up:

   > podman push _<server-address>_/<container-name>:<tag name>
   --tls-verify=false --sign-by<reference to the gpg key on your local>

   If the image is not signed, it can only be pushed with any current signature embedded.

4. Push the image without signing it:

   > podman push _<server-address>_/<container-name>:<tag name>
   --tls-verify=false

5. Navigate to the automation hub and click on Execution Environments if that window is not open.
6. Click the Refresh icon to refresh the page to show the new execution environment.
7. Click the name of the image.

1. Click the image name to open the details page.

2. Click the three dots in the upper right hand corner of the details page. Three options are available:

   • Use in Controller
   • Delete
   • Sign
3. Click sign from the drop-down menu.

Procedure

1. In a terminal type:

   > sudo <name of editor> __/etc/containers/policy.json__

1. Under the <server-address> entry, modify the keyPath <1> to reflect the name of your key file.

       {
           "default": [{"type": "reject"}],
           "transports": {
               "docker": {
                 "quay.io": [{"type": "insecureAcceptAnything}],
                 "docker.io": [{"type": "insecureAcceptAnything}],
                 "_<server-address>_1": [
                   {
                       "type": "signedBy",
                       "keyType": "GPGKeys",
                       "keyPath": "/tmp/<key file name", 1
                       "signedIdentity": {
                         "type": "remapIdentity",
                         "prefix": "_<server-address>_",
                         "signedPrefix": "0.0.0.0:8002"
       }

2. Save and close the file.
3. Pull the file using podman, or your client of choice:

Procedure

1. Navigate to Execution Environments.
2. On the container repository you would like to delete, click the More Actions icon ⋮, then click Delete.
3. When presented with the confirmation message, click the checkbox, then click Delete.