The development container demonstration to create a container in which you can use your Visual Studio Code editor in a well-defined development environment includes a shell script (bld.sh) to make the process of running the demonstration as easy as possible. This topic lists and describes the parameters that you can specify when running bld.sh.
To obtain the bld.sh installation script, installable executable, and other files mentioned below, extract the provided .tar file into an empty directory on the container host machine. The files for the base release will be in a DevHub directory within the .tar file; the files for a patch update will be in the main directory extracted from the .tar file.
./bld.sh { IacceptEULA devcontainer [options] }
options enables you to specify a number of characteristics for the image, such as any ODBC or Java requirements, or auto-login credentials. For a full list of available options and their definitions, run ./bld.sh without specifying any other parameters.
The DevContainer directory, within the Examples directory installed with the development product, contains a number of COBOL projects that you can open within the development container. This directory also contains a script that prepares the devcontainer.json files for each of those projects - this file is necessary to link the project with the development container.
Follow the on-screen instructions to run the preparation script.
The file specified as a parameter is an environment file that was generated during the creation of the dev container base image, containing the required environment settings to link each project with the container. The contents of this file is used to populate the ./<project>/.devcontainer/local/devcontainer.json file.
A development container is started and the project is opened within it. When you close the project, default behavior is that the container is stopped. This behavior can be changed by editing devcontainer.json; see https://code.visualstudio.com/docs/devcontainers/containers.