Images vs. Containers about docker-csgo HOT 2 CLOSED

So if I were to start the image docker-csgo:pug-practice it's already installed and runs the server in seconds with a concrete set of packages (steam client, metamod, sourcemod, practivemode, etc..).

This is not 100% correct. You need to mount a volume to the container where the server files will be installed (as explained here). The image takes care of automating the server installation and optionally installing all the mods as well depending on the image. The volume is the state.

Configuration would be done over ENV_VARS just like now, but starting a container would not install or update the dependencies again.

This definitely would have some drawbacks like a higher maintenance burden, but most of it could be automated.

This is not correct. Any environment variable ending with _VERSION can be changed and will trigger an update or downgrade on container start.

What are the reasons that the installation of the server, plugins, etc. is part of the container's CMD (entry-point)? Couldn't we make this part of the image build process?

The server files are too big for an image (around 20 GB). Also some files must be stored in a volume.

You should try to read and go through the shell scripts to get an understanding what is happening:

• https://github.com/timche/docker-csgo/blob/main/base/server.sh
• https://github.com/timche/docker-csgo/blob/main/sourcemod/server_sourcemod.sh
• https://github.com/timche/docker-csgo/blob/main/pug-practice/server_pug_practice.sh

from docker-csgo.

Thank you so much for your quick reply. It does make a lot more sense now ✌️

The obvious thing I was missing is the size of the server files. A container image of 20GB would be ridiculous.

from docker-csgo.