Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Size #39

Open
Wriman opened this issue Feb 4, 2020 · 3 comments
Open

Size #39

Wriman opened this issue Feb 4, 2020 · 3 comments

Comments

@Wriman
Copy link

Wriman commented Feb 4, 2020

Hello! How many space need this image?

@surister
Copy link

surister commented Feb 4, 2020

Doesn't work so doesn't matter.

@NightDragon1
Copy link

What's not working?

@Marakai
Copy link

Marakai commented Mar 8, 2020

The size shouldn't be too bad as all the "big" stuff is mapped via the /ark volume: the Steam server tools and the game itself. Only the arkmanager package is stored locally. That said, the image could be far more compact, if it followed Docker's best practises for creating compact images and optimising layers and caches. E.g. instead of all the separate RUN statements, combine them into one with '' separators, thereby creating a single layer.

https://www.docker.com/blog/intro-guide-to-dockerfile-best-practices/

I'm not sure a gigantic monolithic system like Ark Survical lends itself to containers. If only it could be run as a cluster of many smaller ones. :(

The server tools on my EC2 spot come in at 11GB, the game itself with a moderate amount of mods at 21GB. At runtime, a single instance Valguero map will make the server gobble up 16GB RAM like nothing. Hardly in line with the Docker philosophy of swarms/clusters of small immutable containers. :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants