Troubleshooting

You can troubleshoot the container by opening a shell within the container. Add the flag -it to the container run command to open an interactive shell within the container, and remove the -c flag from the /bin/bash command. For example:

docker run -it --rm \
  -v ${HOST_DIR_SRC_CODE}:/data/src \
  -v ${HOST_DIR_TOOLKIT_DATA}:/toolkit-data \
  -it
  ${TOOLKIT_IMAGE} /bin/bash

You can then run commands within the container to troubleshoot any issues you are facing.

You can set environment variables by passing the -e argument when using the container run command. For example, the following command sets the environment variable MY_VAR to my-value:

docker run -it --rm \
  -v ${HOST_DIR_SRC_CODE}:/data/src \
  -v ${HOST_DIR_TOOLKIT_DATA}:/toolkit-data \
  -e MY_VAR=my-value \
  ${TOOLKIT_IMAGE} /bin/bash -c "echo $MY_VAR"

This is useful for setting up environment variables that configure the behavior of the utilities within the container during a command is run.

If you receive the following error message when running the image-scan utility to scan an image from a container registry, you may need to skip TLS verification when connecting to the registry:

x509: certificate signed by unknown authority