persistent editing of settings

[soupcanx]

Apologies for making this an issue, but i'm not sure how else to contact. How can one persist settings on the default server launch.

for example - when docker-compose up -d, i'd like it to just server up a ffa server that starts immediately. I can docker-compose exec mvdsv /bin/bash and edit ktx/ktx.cfg for example, But these changes do not persist.

attempting to add lines to the volume section in docker compose has failed as well.

I feel like i'm missing something here - or is it a static configs in general and that expect settings to be chagned with rcon after launch?

[eb]

In general it is expected behavior that changes to a running Docker container don't persist. Stopping and starting a container usually still has your changes, but as soon as the container is recreated all your changes that are not on a volume or bind mount will be reverted to their initial state.

Anyway, in the case of this particular set of Docker images, you're not even able to do any changes to the configs and make them persist between container restarts. That's because the entrypoint.sh script of the mvdsv service overwrites them every time.

I'm curently working on a new set of Docker images for nQuakesv that should not exhibit this issue. Not sure when this is going to be finished though. Could be a couple of more weeks. Maybe you should use nQuake/server-linux in the meantime.

[nvtkaszpir]

There is another option to mount specific directories as volumes, but that would require docker-compose rewrite.
Some ideas are in #1 (comment)