Starting to Debug a COBOL Application in a Container

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

Once your base image is running and you have found out its ID or IP address you are ready to use Visual COBOL to connect to the container using remote debugging.

If you have followed the steps outlined in Building a COBOL Application that is to be Debugged in a ContainerRunning a Container that is to be Debugged and Finding the Details of a Container that is to be Debugged you will have a container that isn't yet running your COBOL application but is waiting for you to connect to it using Visual COBOL. See To start debugging a COBOL application that is not yet running in a container for full information on how to do this.

Note: If you have a debuggable COBOL application that is already running in a container you can still connect to the application and debug it. See To start debugging a COBOL application that is already running in a container for more information on how to do this.