Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
vs
Running an entirely headless system in Docker which is already secure by default.
Each to their own I guess.
A VPS is headless...and you still have to secure whatever docker is running on as well as trust that the container was created with everything up to date with no malicious software.
VPS -> Core Keeper Server
vs.
Server -> Docker -> Container -> Core Keeper Server
I suppose you could consider screen an extra step but it's really simple to use.
I'm already familiar with running steam servers this way (years ago I managed many servers for our gaming clan and hosting service we provided), so it makes sense to cut out the extra Docker software. I also wanted to configure the server anyway, so I knew I'd be digging into the config file to customize it.
Setting up steamcmd was quite easy. The Core Keeper devs even included a one liner to install it: steamcmd +login anonymous +app_update 1007 +app_update 1963720 +quit
I chose a VPS so I don't have to host it on an old machine at home and configure a vlan. It also ensures a more central location for friends in a datacenter with a great connection. I'd go with a dedicated or colocation if it wasn't more expensive, but for $13/month a VPS works just fine. I can always request more CPU cores and RAM too.
Docker seems like a great way to make it easy to share software, so if you're more comfortable with that, then go for it.
The goal is to play Core Keeper with friends and have fun after all.
Might help for the exact commands or can just use it to build a new server. Don't hate me if it messes up lol.
https://cloud.linode.com/stackscripts/1041800
Used Grubheads commands links and services file lol. Thats why I thought to post it here.
Wanted to learn about docker so I made a docker image too if someone wanted to use that.
https://hub.docker.com/repository/docker/crashoverridee/corekeeper
Did you make update sto the launch script?
It's trying to kill a process that doesn't exist. Did you happen to manually specify a pid in the _launch.sh script directly? It isn't meant to be updated by the user so make sure you didn't manually set the pid in there. You can probably rename it and force a server update with the steamcmd to make sure you have a fresh copy of the script.
See if you can get it working without running it as a service first. I don't work on the game and don't make changes to the _launch.sh script. I don't believe they changed it, but it may have been updated in the latest updates.
That line 10 is looking for a variable which should contain the pid of the core keeper server. Later in the script, it uses "ckpid=$!" which should grab the last background process created, I believe.
Perhaps you have extra Core Keeper services running? You could use the "top" or "ps -A" to view the process ID's and names to see if there's a duplicate running. Then, kill the extra ones and try starting the server again.
I did find that when I go to stop the server to run an update, stopping the service doesn't seem to stop the server, so I manually kill the server as well after stopping the service. This might be because I have it set to automatically restart the server, or it's not handling the process automatically. There is a forking option for services, but I didn't go that route.
Let me know if you get it working or not. :)
mkdir ~/.steam/sdk64
ln -s ~/.steam/steamcmd/linux64/steamclient.so ~/.steam/sdk64/steamclient.so
I tried to use this Stackscript today but when I enter the Game ID I created into Core Keeper, I get an error "could not find game". Am I missing a step between running the StackScript & then connecting to the game created on the server?
May make sure your ports are forwarded 27015-27016 in firewalls under inbound rules you will want to accept those for the steam ports.
Also they may have increased the size of the gameID I noticed I had to increase mine a bit for it to work.
I see you posted this on Feb. Me and my friends were trying to use the server for the Valentines event but for some reason I couldn't connect to it until the next update. Not sure what happened? I really didn't see any fixes about it, but I think it was something on corekeepers or steams end? So we wound up using an world on one of our pcs lol.
Hope that helps. I've been using my docker image since then since it is easier to move between servers and backup, but it has quite the learning curve.
I put together a github respoitory with my docker-compose.yml that should make it super simple.
https://github.com/maxss280/corekeeper_docker