Steam telepítése
belépés
|
nyelv
简体中文 (egyszerűsített kínai)
繁體中文 (hagyományos kínai)
日本語 (japán)
한국어 (koreai)
ไทย (thai)
Български (bolgár)
Čeština (cseh)
Dansk (dán)
Deutsch (német)
English (angol)
Español - España (spanyolországi spanyol)
Español - Latinoamérica (latin-amerikai spanyol)
Ελληνικά (görög)
Français (francia)
Italiano (olasz)
Bahasa Indonesia (indonéz)
Nederlands (holland)
Norsk (norvég)
Polski (lengyel)
Português (portugáliai portugál)
Português - Brasil (brazíliai portugál)
Română (román)
Русский (orosz)
Suomi (finn)
Svenska (svéd)
Türkçe (török)
Tiếng Việt (vietnámi)
Українська (ukrán)
Fordítási probléma jelentése
Filter for "aircodes ARKCLUSTER-XEON" or open 138.201.134.179:7777
I dont know what version of "compose-docker.yml" you are actually using. (mine is tested and working, feel free to contact me via pm)
Be carefull with copy&paste, review the code it might can be broken in case of a wrong formating.
--> you can find the new created Volume "CROSSARKFILES" in
did you add the importend code lines for the "CROSSARKFILES" Docker-Volume?
did you add this parameter to your start script?
So, I built a new server (physical) and used your .yml file. Definitely worked, much appreciated. After looking at my old attempts (I always keep bak files) I did not include the overridedir entry in "" so my assumption is that is what caused it to fail.
Regardless, thank you again, both solutions worked, yours is better.
I agree with Manuel, I used to manage four clustered servers in ASE and I took my Game.ini and GUS.ini and directly imported them with only a few lines needing to be tweaked. Easiest thing to do is load them in Beacon and set the server type to ASA vice ASE and, viola, you're done.
as Scorched Earth is going to be released April 1st, 4PM PST [1] with ScorchedEarth_WP as the map id, I extended the Linux container image guide [2] to cover these topics ...:
* How to run a cluster?
* How to launch servers with Scorched Earth on Linux
There's also a new section at the end of the guide that lists all available map ids. I keep the list updated with new map launches.
Besides that, I also worked on some other improvements and released version 1.3.0 of the container image.
####
# Changelog:
* Enabled cluster support by default in `docker-compose.yml`
* The container image can now use the time zone settings of the host system. Please make sure to pass `/etc/localtime` to the container as read-only volume. [3]
* Improved README
* Added an explanation how to add cluster support
* Added an explanation for volume `cluster-shared`
* Removed unverified rumor ("Server too far away")
* Added a "Common Issues" section
* Added a section regarding mod support
* Updated required disk space
####
Let me know if you need any help with your server setup, either in this thread or on GitHub.
[1] https://survivetheark.com/index.php?/forums/topic/727874-scorched-earth-and-bobs-tall-tales-launch-details/
[2] https://github.com/mschnitzer/ark-survival-ascended-linux-container-image/tree/main?tab=readme-ov-file#ark-survival-ascended---dedicated-linux-server---docker-image
[3] https://github.com/mschnitzer/ark-survival-ascended-linux-container-image/blob/5ff99cbd363b3ccc951b0eb473e53f365496b34c/docker-compose.yml#L24
I’m on step 4, but when I try ‘docker-compose up -d’ I get a response of “Command ‘docker-compose’ not found, but can be installed with: Snap install docker”.
I’m not sure what to do.
*edit:
It says I have Docker version 26.0.2 and Docker Compose v2.26.1 installed
*edit2:
Removed the ‘-‘ in the command line and it seemed to work. Server started for the first time but now the given session ID does not show up when trying to connect.
As for the server not showing up, please follow these steps:
https://github.com/mschnitzer/ark-survival-ascended-linux-container-image?tab=readme-ov-file#common-issues
Interestingly, I tried other images - a similar situation. As soon as the line “Starting a dedicated server ARK: Survival Ascended...” appears, it immediately "crashes" with code 0
I read other comments on this problem, tried deleting and downloading the server files again - it didn’t help(
I don’t use virtualization anywhere
Any ideas what could be wrong?
Docker version 26.0.0, build 2ae903e
Docker Compose version v2.25.0
I'm trying to run on a VPS)
Interestingly, the Enshrouded server (https://hub.docker.com/r/sknnr/enshrouded-dedicated-server), also with proton, started without problems (docker compose), but ARK doesn’t want to)
The Vallheim server also started absolutely without problems (but there is no proton there)
Do you think there is not enough RAM and that’s why this error occurs? I think it’s unlikely that this is connected, but anything can happen))
Or... does it really start, but crashes due to lack of resources?) seems to be true...
So you need to have at least 11 GB of RAM just to run the server (without any players on it). So I'd say go with 13 GB for now if nothing else runs on the server.
The changelog on GitHub:
https://github.com/mschnitzer/ark-survival-ascended-linux-container-image/releases/tag/1.4.0
# Changelog
* Updated the container image to openSUSE Leap 15.6
* Added a list of all available maps with their id
* Added a `docker-compose.yml` example for map Scorched Earth in a cluster setup scenario
* Updated required disk space for an ASA server
* Added support for ASA plugins
* Significantly reduced the container image size (by ~412 MB of compressed size). Proton will therefore no longer be shipped with this image, but it will be downloaded and installed automatically instead.
* Updated README
** Added a suggestion to change the `-clusterid` option
** Added a section to explain how to add plugins from gameservershub.com
** Added a section to explain how to update to a newer version of this container image
# Breaking Changes
If you follow the instructions to add plugin support to your server, as described in the README, then you need to add `tty: true` to your `docker-compose.yml` file below `image:` (or anywhere else in the same hierarchy as `image`). If you don't plan to add plugins to your server, then you don't need to change anything, but we advise you to always follow the latest `docker-compose.yml` definition that we use.