Reset of location path of instance after container...
# umh-support
u
After a restart of the container, the instance reverts to an earlier state of the location path. Is there, beside the config.yaml, any location where an initial location path is stored?
j
what do you mean? could it maybe through docker compose or some env variables that you have set?
if you set LOCATION_0 or something it will be overwritten
u
yes, Location_0 ... location_6 are replaced with the initial values used when the container was first connected to the management console, overwriting the settings in the current config.yaml for Location_..
only for the location of the instance
yes, you are correct, the env config for the container contains a diffrent set of location entries
I think they were set during the initial set up of the container, so I am not sure how to remove or persistenly change them
r
How have you started the umh-core? using a docker-compose.yaml ? if so the location_0 is in the docker-compose file
u
I used the command that was compiled by the management interface, that included the settings probably
r
ah. i see. do you have the api token saved anywhere ? Or else you will need to exec in to the pod and echo the env variables to get the api token and the other env variables. Save them somewhere, stop the container, then start again with the same command but this time with the changed location value. This is the only way i know, but i just found that there might be a shortcut to this. "You just stop docker daemon and change container config in /var/lib/docker/containers/[container-id]/config.json (sic)" and start the daemon again. https://stackoverflow.com/questions/27812548/how-to-set-an-environment-variable-in-a-running-docker-container
u
Thank you, I will try it, otherwise I'll just backup the current config.yaml and nuke the whole container
7 Views