Finding the Details of a Container that is to be Debugged

Note: This topic does not apply if you are using Visual COBOL Development Hub as a stand-alone development environment.

Note: This topic only applies to using JVM COBOL applications in containers. To use native COBOL applications in containers you need to use the functionality described in Debugging and Running Native COBOL Applications in Containers.

Once the container to be debugged is running you need to find out some identifying information about it that you can then specify to Visual COBOL so that you can connect to the container to start debugging it.

You can specify either of the following pieces of information to Visual COBOL:

The container's ID.
To display summary information of all running containers (including their IDs) enter the following command:
```
docker ps
```
or:
```
podman ps
```
The container's IP address.
To find the IP address used by a running container you use the docker inspect or podman inspect command. The docker inspect or podman inspect command can return a wide range of information, but to return the IP address of a container the format of the docker inspect or podman inspect command is shown below:
```
docker inspect -f '{{range.NetworkSettings.Networks}}{{.IPAddress}}{{end}}' container-name-or-id
```
or:
```
podman inspect -f '{{range.NetworkSettings.Networks}}{{.IPAddress}}{{end}}' container-name-or-id
```
So, for example, to find the IP address of the container that would have been started by the docker run or podman run command in Running a Container that is to be Debugged you could use the following command:
```
docker inspect -f '{{range.NetworkSettings.Networks}}{{.IPAddress}}{{end}}' helloworld-x64-debug
```
or:
```
podman inspect -f '{{range.NetworkSettings.Networks}}{{.IPAddress}}{{end}}' helloworld-x64-debug
```
When you have found the IP address, you need to confirm that it is reachable from where you are debugging.