Why do you use docker in the first place?

If you need to know the auth cache (which is probably in $HOME/.steam/ somewhere, since Steam does not honor FHS), the easiest thing to do it is to use find prior and after login with mtime.

Thanks for the answer. I like the idea of having my servers in separate containers, that i could easily start/stop/duplicate/rollback from an interface like weavescope. It also makes network easier : I can just start n copies of a csgo server and bind them to a different outside port using docker. It also feels like a good idea to have a complete separation of the servers (instead of having a lot of system users csgo-1 csgo-2 etc)

You definetely helped me. I think the credential files are the ones starting with ssfn****. I'll try and find a way to share them between the containers.

Originally posted by Biggie cheese:

Thanks for the answer. I like the idea of having my servers in separate containers, that i could easily start/stop/duplicate/rollback from an interface like weavescope. It also makes network easier : I can just start n copies of a csgo server and bind them to a different outside port using docker. It also feels like a good idea to have a complete separation of the servers (instead of having a lot of system users csgo-1 csgo-2 etc)

You definetely helped me. I think the credential files are the ones starting with ssfn****. I'll try and find a way to share them between the containers.

You're better off using one container for your steamcmd, then volume mount home and the different game servers into separate volumes. After you have that "manager" container downloading workshop files, run game servers in their own containers volume mounted to the parts they need.