Running utilities from the

To run utilities, enter the container and use a bash shell.

Before you begin

If you store configuration and data files in the , they will be lost the next time you upgrade or restart the Utility server image. The and other containers are also not intended to hold large amounts of data. To avoid this, place any files that could be changed into a separate volume mounted to the container as a writable directory. Ensure that all configuration files and data files are written to this directory. Now, when you upgrade the Utility server Docker image, the files you changed in the are not lost. You need only again mount the volume to the new Docker container. The files in the directory are also accessible in the host machine, where editing files may be more convenient.
Important: Beginning in 9.1.14.0, application container images are built to be run as a non-root user by default. You must account for this change when using a mounted volume to access files from the , as existing file permissions may not allow for access by the non-root user. For more information, see ../../../install/concepts/ciginstall_nonrootdocker.html.
If you have customizations that must accessed by utilities in the , build a custom Docker image for them and put your changes there. See ../../../install/tasks/tiginstall_updatedocker.html.

Run docker ps to verify that your containers are running.
Locate your utility container name in the NAMES column.
For example, myproject_utils_1.
Start a bash shell by running the following command with the utility container name
```
docker exec -it <utility_container_name> bash
```
Go to the bin directory.
```
cd /opt/WebSphere/CommerceServer90/bin
```
Run the utility that you need.