You can SCP missions into /home/steam/mpmissions like so: You just need to get your missions/scenarios into the /home/steam/mpmissions volume some how, and below are a couple of ways of doing that. If you would like to access the server then you can ssh in, run su steam and tmux attach to get to the running server.
The steam user has limited access to the file system and is mostly locked down to the /home/steam directory. The server is ran inside of a tmux session under the steam user. It will give you a yes/no prompt asking if you want to overwrite the old data with a new fresh configuration.Īfter you start a new container one easy way that you can check if your server is running is by using the server browser by BIS (make sure to add your server's IP and steam query port so that the browser knows about your server) run.sh and giving the same name for the data container. You can reuse the same data and restart the server by using. Make sure to edit the configuration files to your liking, they will persist between runs. The script links the volumes from the data container to the server, allowing you to edit configurations and mods without losing your changes.įrom here, you should see your game show up in the server browser after a few seconds. Next, an arma3 server container is created and ran, using the volumes from the data container as data storage. This prompts you for a name and sets up a data container to hold your mods, mpmissions and configuration settings. NOTE: You should use your junk steam account, or create one if you haven't already and start using it for your dedicated server instances.
#Arma 3 servers down install
You will get prompted to password protect the ssh key used to connect to the container after its running, and for steam account credentials so that the build can install the arma 3 dedicated server tools.
#Arma 3 servers down how to
How to useįor Ubuntu trusty 14.04, just do wget -qO- | sh Lastly, there is a prebuilt image available on Docker Hub. home/steam/mpmissions: The mp missions folder profiles: The server user profile settings configuration: The server.cfg and the basic.cfg files There are a few volumes set up in this container: Take a look at the nf to see all of the alterations. This container also ships with tmux and vim installed and some dot files that modify some tmux settings. This should allow you to ssh in and do anything you may need to do inside of the container remotely without having to tear it down and start it up again. This container has an ssh server set up and listening on container port 22. It supports mods, SSH and persistent configuration via volumes. This is a dockerfile for running an Arma 3 dedicated server.