| 7 Nov 2024 |
 setop | definitely not in debug
debug is enabled in "dev" and is very very verbose. | 10:15:42 |
| setop | * definitely not in debug.
debug is enabled in "dev" and is very very verbose. | 10:16:13 |
 neil | That's what I was hoping for but editing my .env and restarting the containers with sudo docker compose restart doesn't seem to work.. let me try making the postgres passwords wrong just to see if my changes are actually doing anything :/ | 10:16:39 |
| setop | you must not only restart | 10:17:00 |
| setop | you must recreate them | 10:17:07 |
| setop | env is only taken when creating | 10:17:16 |
| setop | then it is immutable | 10:17:30 |
| setop | of you must change the env from the inside of the container by modifying the entrypoint | 10:17:55 |
| neil | What is the docker command to do that? | 10:18:03 |
| setop | I usually use docker compose which does it automatically. | 10:18:29 |
| setop | but with bare docker | 10:18:35 |
| neil | That's what I thought I was doing.. docker compose restart isn't enough? | 10:18:43 |
| setop | you must delete the existing "api" container | 10:18:54 |
| setop | then docker run gain | 10:19:03 |
| setop | * then docker run again | 10:19:25 |
| setop | * you must delete the existing "api" container (docker rm -f) | 10:19:50 |
 javahippie | neil: To add to your other question: Debug Level logs work for us, but I'm not sure if a "docker compose restart" is sufficient to update the config, we used "docker compose down" and "docker compose up" and the config changes worked | 10:19:52 |
| neil | Ah, so docker compose stop; docker compose rm; docker compose up -d | 10:21:44 |
| neil | Thank you setop, that was a vital step I was missing.. I have logs at least now! | 10:21:56 |
| setop | event docker compose up -dwill detect change in in the container description and recreate it. | 10:22:18 |
| setop | * even docker compose up -dwill detect change in in the container description and recreate it. | 10:22:42 |
| neil | I thought so, but it complained containers need to be removed first | 10:22:55 |
| setop | I might be lucky : I set the four env vars in docker and it worked out of the box for OVH mail. | 10:23:57 |
| neil | Actually, that did seem to work now, I must have started this incorrectly in the first place. | 10:24:57 |
| neil | Thanks all, that seems to have been my problem, not familiar enough with docker (and was forced to use it as I had a too old version of libc6 on my debian server) | 10:26:26 |
 cos | Shouldn't restart == (down up)? | 10:27:49 |
| neil | I think restart misses the remove step | 10:28:15 |
| neil | (which is needed for the create) | 10:28:31 |
| setop | maybe because you did not create it with composebut with run. | 10:30:02 |
| setop | in any case, yes it must be removed before creating. | 10:30:18 |
