Note: This topic only applies to using native COBOL applications and native
COBOL Unit Test projects in containers. To use
JVM COBOL applications in containers you need to use the functionality described in
Debugging and Running
JVM COBOL Applications in Containers.
You set container-related properties for a project by clicking
.
The container-related properties you can specify are as follows:
- Context
- The build context to use when building the image for this project.
- Build arguments
- Additional arguments to specify for the
docker build or
podman build command when building this project.
- Run arguments
- Additional arguments to specify for the
docker run or
podman run command when building this project.
- Dockerfile
- The name of the Dockerfile for this project.
- Base stage
- The name of the base stage in the Dockerfile for this project. This is the stage of the Dockerfile that is run when using
"build on host" mode running and debugging.
- Mappings
- Volume mount details for this project.
The settings specified here for
Run arguments and
Mappings can be overridden by the currently active debug and run configurations.
The settings specified here for
Context,
Dockerfile, and
Base stage are used by the New Dockerfile wizard creating a Dockerfile.
Additional Project Properties for Containers when using
COBOL Server
If your COBOL application uses
COBOL Server (for example, if building a SOAP, REST, or Enterprise Java Bean service) and is targeted for containers, you'll need to request
that the application files are packaged as a
.car file. To do this, set
Package services as COBOL archive (.car) files to
Yes from
.