Finding the Details of a Container that is to be Debugged

Note: The information in this topic applies to both native COBOL and .NET COBOL applications unless specifically indicated. If you want to use native COBOL in containers, however, Micro Focus recommends using the IDE-based functionality described in Debugging and Running Native COBOL Applications in Containers as it offers an fully-integrated, easy-to-use debugging experience.

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
```
The container's IP address.
To find the IP address used by a running container you use the docker inspect command. The docker inspect command can return a wide range of information, but to return the IP address of a container the format of the docker inspect command is shown below:
```
docker 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 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
```
When you have found the IP address, you need to confirm that it is reachable from where you are debugging.