The repository URL, including the protocol part, such as. Values must be one of: FTP, HTTP or HTTPS. The protocol to use for data transfer with this repository. If blank, the container will ignore the repository creation and proceed as usual.
It must be a valid identifier and this name can used for other commands such as -build. This repository will be created on every container start, unless a repository with this name already exists.
This variable is the name of a repository that will be created by arma3sync-docker when starting. All you have to do is to provide the follwing environment variables with values. Environment variablesĪrma3sync-docker can use the environment variables to to initialize a repository. Note: Arma3Sync 1.6 is not available because it uses Java EE components which are not available with recent jre version. Arma3sync versionsĪrma3Sync-docker provides images for the following versions of Arma3Sync: Note: Due to a bug in Github's runner engine matrix build system, I'm not able to provide shorter tags. jre17, current LTS version of the runtime.jre8, version used by arma3sync developpers.The complete list of tags is available on the project's Docker hub page.įor production usage, you should use arwynfr/arma3sync:1.7.107-jre8 OpenJDK versionsĪrma3Sync-docker provides images for the following versions of the OpenJDK runtime: You can specify major or minor version of arma3sync and optionally major versions of the jre.
How to use arma3sync-docker Image settings TagsĪrma3sync-docker provides multiple tags allowing to run different combinations of the software and the java runtime versions.
0 kommentar(er)
