You should be aware of the following limitations when using
Enterprise Developer with containers:
Debugging
- On Ubuntu, in order for debugging to work within a Docker version 18.04 Container, you must update the kernel of the Docker
host from version 5.0.0-27 to 5.0.0-31.
- When debugging a COBOL application in a container, you cannot provide input to or see output from the application.
Docker for Windows
For information on reporting or troubleshooting issues with Docker for Windows, see
Docker: Logs and Troubleshooting or
GitHub: Docker for Windows Issues.
General
- Java is supported from version 17 onwards.
- It is not possible to containerize COBOL applications using lightweight operating systems such as CoreOS Container Linux,
SUSE MicroOS and Alpine Linux.
- It is not possible to run COBOL applications in containers on Linux on PowerPC or S/390 chipsets.
- Using the
Micro Focus Support Scan Utility,
MFSupportInfo, in a container is not supported on Windows.
- The
microsoft/windowsservercore image only supports the English language so you cannot use any other languages in images based on that image.
The base images for
Enterprise Developer Build Tools for Windows that are created by the Docker demonstrations are based on the
microsoft/dotnet-framework image (which is based on the
microsoft/windowsservercore image), so this restriction applies to any images created using the Docker demonstrations.
Operating Systems
Enterprise Developer is supported for use with Docker on the following Intel 64-bit operating systems:
- Windows 10 (Pro or Enterprise editions) with Hyper-V enabled
- Windows Server 2016
Note: Docker cannot be used on a PC that has VirtualBox or VMware installed.
Use with
Enterprise Developer Products
- It is not possible to containerize a COBOL application that runs under
Enterprise Server for .NET.
- If a region is hosted within a container which does not or cannot expose its internal network addresses, the
Micro Focus Enterprise Server Common Web Administration interface will be unable to connect to the started region's ESMAC/monitor configuration unless the MFDS_EXTERNAL_ADDR environment
variable is set within the container to an externally contactable address.