Hi, I'm trying to make a dedicated Arma 3 server with docker, everything works perfect except that the server is constantly restarting. Every few seconds it is connecting to Steam (even after having already connected) which means that after a while it gives you an error due to the ratelimit that Steam has, and that also happens with the process of starting the server, first everything starts correctly and just at the moment it starts it restarts and so on all the time in a loop.
I would ask for Arma 3 Container: Is it possible to install and manage Mods from Steamworkshop with your Container? If yes, how? If not, can you implement Mod Support? Something like Parameters for WS-IDs, Modfoldername and Support for renaming in lower case? Something like this script:
Mh. Very sad. Because Arma 3 is not really a game. It is a sandbox and nobody plays Arma after a few hours in vanilla. You can find more than 60 thousand mods in the workshop. So it is a mess, if you would manage this manually. Only to be up to date manually is pain.
You can always write a custom "user.sh" script and mount it to '/opt/scripts/user.sh' inside the container to install all your mods, the user.sh is executed always as root and executed before SteamCMD starts, so it should be theoretically possible to install it like this (keep in mind that the game needs to be first fully installed):
Place the script somewhere on your Unraid server (please note you have to write this script in Notepad and not in Wordpad because it will mess up the format an Linux can't read the file) and mount it like this (in this example I have placed the script in '/mnt/user/scripts/arma3.sh', as long as you name it in your container 'user.sh' everything will be fine) :
i mean like you did it in Valheim. If theres an update on rust (what happens quite often latley) Oxide(Umod) everytime gets overritten and you have to manually download and install it again. its pretty tricky if your at work and your friends want to play and you cant to anything.
trying to get Arma3 server up, i left the template config stock w/ the exception of steam login and password. i change the server name in the server.cfg file but i still cant connect to it even if i do a direct connection. all i get is a ARMA3 splash screen. Has any one else had this problem and figured it out?
this Tutorial is for their Website but you will get it, Its just extracting the zip into your gamefolder and Override the existing files. You start the Game as normal Expect that you can install mods/Plugins
Currently I'm don't checking if there was an update, but I'm installing the Oxide Mod every time the container is started/restarted so this should be no problem and since the Oxide Mode is not that big and doesn't contain much files there should be no problem.
I was going to backup my 'worlds' since my original friends have lost interest in the game and start fresh and then restore the world at a later point once more content drops. Then I thought why do that when I can just create another world/container so decided to come here and check before I tried to do something stupid.
Someone already asked the question how to run two instances of a dedicated Valheim server and you referenced this post. I'm looking at your graphic which probably an idiot would understand but I guess I'm lower than idiot status because I don't understand what I'm supposed to do here to create a "new world" or "new server"......
ARK does some post processing of mod, why you ask? I do not know.... They built in a function to the server that uses SteamCMD (in a hard coded location of course) to fetch the files and then it does its thing putting them in another location. If all you want to do is add a mod or two to a single server you add mappings so that your SteamCMD shows up in the place that the server binary is expecting it, and command line arguments to tell the server binary what mods you want installed.
If you want the whole system to check for updates or manage a cluster then I found the best course is to run a separate container that monitors the SteamAPI & arkdedicated.com version numbers then compares that to the local files, if there is a change then it shuts down the ARKs restarts the primary (the first one in the cluster and the one that manages the mods) then restarts the remaining ARKs.
i installed a few mods and i get out of memory issuses sometimes. do you have any clue what to do? i know the server is running in an emulated windows enviroment. but i dont know what to do. i have 64GB ram and the container is not using all of it. i have to manually restart the server if this happens
My Window Server VM is running a few game servers and MySQL databases. How does this get broken out or can it be? Most of the game servers are Steam games (Factorio, Assetto Corsa, Arma 3, etc) but I also have modded Minecraft servers. The MySQL databases are a mix of things: Arma 3 DB, MMO Private Server stuff, and flask development databases. How would I translate this into containers? Multiple MySQL containers? Per database? Can the Steam Servers run in a container? What about the Java Minecraft servers?
You want some kind of automation to setup containers (simplest is docker-compose, complex is ansible). Anything static like configuration is contained within your automation system, and you can bind-mount directories to the container for static files (like TLS certs).
Containers can access directories from the host using either volume mounts or bind mounts e.g. for a webserver you might have a directory on the host where files are stored, and you might have that volume mounted into a samba container and into an apache container.
So i was interested in installing steam on my openmediavault machine in order to host an arma 3 server, however when i serached this forum, theres no information about how to install steam or steamCMD, so i was just wondering if anyone has tried this before and possibly could help me set this up correctly?
I'm running a Starbound server with SteamCMD. You more or less only have to follow the guide you posted. The only thing you may have to do except that is to run dpkg --add-architecture i386 and install appropriate packages.
Am trying to enable registry on my gitlab-ce instance but connection to it is not working, neither there are errors.
My setup is linux server, with gitlab-ce docker container and registry enabled in it(no separate container for registry).
What i dont see, and what i think is problem, is my host listening on that port. I see on linux ports 80, 443 and 22(those ports are coming from gitlab container) but i do not see 5005 or 5050, and i cant telnet to ip-host:port.
But also when i try to connect to repository with docker login registry.gitlab2.arma:5005 i get connection refused. Small not about gitlab, if you try completely imaginary url, e.g. docker login 550.550.550.550 it will not reject but it will ask you for user pass, i find that making debugging even more challenging.
what i find problematic is that there is nothing in logs about this refused connection(which i understand since my host is not listening on port 5005 and connection never comes to it), but there is nothing in logs about nginx not starting the registry or reason why it does not listen on that port or anything like that, so i cannot find anywhere what the exact problem is.
I entered container to check it and its not listening on loopback:5005(so i dont see it on host), it just not listening on that port.
I have found nginx conf file for registry and it seams ok.
Did you expose the 5005 port with docker? If not, then perhaps easier way is have two hostnames, gitlab.mydomain.com and gitlab-registry.mydomain.com so that the nginx proxy can deal with which one is for registry and which one is for normal gitlab commits, etc. Then just access it over port 80 or 443 which you already have exposed.
i want us to understand each other completely and this i dont understand 100%. There is no need for registry to be really open for external access(from outside of scope of my local network), but i want it to be accessible from my local network, just like gitlab instance is. My docker-compose file is dealing with that and i think thats ok:
One other idea I had while reading the docs - enable the Registry debug server from the docker-compose config, restart docker-compose, exec into the running container again, and run the curl commands to request the debug output from the server.
Try changing the port to 6000 and see if the behaviour changes. If it starts to work - restart Docker, and the host VM to clear out stale sockets. Investigate the startup routines if there are services that bind port 5005.
I had a peek into GitLab - ArchWiki but there is no mention of the registry, except for the config options. The source install uses a different location with gitlab.yml, than the Omnibus package installed in the Docker container. Looking at the options to configure the Puma webserver differently, a socket problem is a good first strategy to debug imho.
c80f0f1006