4.9. Troubleshooting the gcc-toolset-15 container image

Identify and resolve common issues when pulling or running the gcc-toolset-15 container image.

Common issues when pulling images

If podman pull fails:

Check registry login by running podman login <REGISTRY>.
Verify network connectivity to the registry.
Confirm that <REGISTRY>, <NAMESPACE>, and <TAG> values are correct.
If access is denied, verify that your subscription and registry permissions allow access to the gcc-toolset-15 image.

Common issues when running containers

If podman run fails:

Verify that the image is available locally by running podman images <REGISTRY>/<NAMESPACE>/gcc-toolset-15.
The output should display a table row containing the repository, tag, image ID, and size. For example:
```
REPOSITORY                            TAG     IMAGE ID      CREATED     SIZE
registry.redhat.io/.../gcc-toolset-15 latest  a1b2c3d4e5f6  2 days ago  540MB
```
Check volume mount paths to ensure that host directories exist and that you have appropriate permissions.
Review container exit codes and logs to identify script or compiler errors.

Collecting data for support

When opening a support case, collect the following data:

The exact podman commands that you ran.
Full command output and error messages.
The values of <REGISTRY>, <NAMESPACE>, and <TAG> that you used.
Information about the host, including Red Hat Enterprise Linux version and architecture.