Docker parameters
Note: For more information on parameters, see the Docker
documentation.
| Parameter | Purpose | Required | See Also |
|---|---|---|---|
| -i | Run interactively. Pair with -t. | No. However, not specifying these parameters can result in terminal errors on the console that uses docker exec. | |
| -t | Run with a tty session. Pair with -i. | No. However, not specifying these parameters can result in terminal errors on the console that uses docker exec. | |
| -d | Run a Container that is detached in the background. | No. However, the Accesser Container runs in the foreground if this parameter is not specified. | |
| --env | Each environment variable to be specified. Each needs its own --env parameter. | Yes | Container environment variables |
| -v | Volume to bind and mount from the host OS into the Accesser Container persistent area. The host directory must be writeable, the directory cannot be shared between Container instances and the directory must be unique. | No, for basic Container functions. Yes, for a Container upgrade or viewing Container application logs with host tools. | appliancecontainerfdd_upgrade_a_container.html#appliancecontainerfdd_upgrade_a_container |
| --net | Used to change the networking mode of the Container. However, appliance Containers support both --net="host" and --net="bridge". Only one Container started with --net="host" can be running on a single machine at a time. | Yes | Container network configuration |
| -p | Host port to bind a Container port. | Yes, when using --net="bridge" | Network ports |
| --hostname | Set the hostname of the Container. | Yes, when using --net="bridge". A specified Container hostname is needed for Container upgrade when upgrading --net="bridge" containers. The default hostname that is provided by Docker (based on the Container ID) is not sufficient. The hostname must not be set to localhost. | appliancecontainerfdd_upgrade_a_container.html#appliancecontainerfdd_upgrade_a_container |
| -- security-opt | Override the default security profile. Currently Appliance Containers support --security-opt=no-new-privileges:true, which prevents processes within the Appliance Containers gaining new privileges. | No. Setting --security-opt=no-new-privileges:true is recommended for best security practices. |