fix: increase timeout on the container #299

Merged
fricklerhandwerk merged 2 commits from container-timeout into main 2024-10-30 14:23:12 +00:00
fricklerhandwerk commented 2024-10-30 11:39:19 +00:00 (Migrated from github.com)

since migrations may be quite expensive when the datase state diverges
enough, the container will get killed before it's ready even if
everything is alright. the logs are quite opaque in that case,
because, well, there's no failure.

since migrations may be quite expensive when the datase state diverges enough, the container will get killed before it's ready even if everything is alright. the logs are quite opaque in that case, because, well, there's no failure.
RaitoBezarius commented 2024-10-30 11:40:28 +00:00 (Migrated from github.com)

should be put in the general module, not only this one

should be put in the general module, not only this one
RaitoBezarius (Migrated from github.com) reviewed 2024-10-30 12:05:34 +00:00
RaitoBezarius (Migrated from github.com) commented 2024-10-30 12:05:34 +00:00

mkDefault it

mkDefault it
fricklerhandwerk (Migrated from github.com) reviewed 2024-10-30 12:32:19 +00:00
fricklerhandwerk (Migrated from github.com) commented 2024-10-30 12:32:19 +00:00
          serviceConfig.TimeoutStartSec = lib.mkDefault "10m";
```suggestion serviceConfig.TimeoutStartSec = lib.mkDefault "10m"; ```
RaitoBezarius (Migrated from github.com) approved these changes 2024-10-30 12:37:50 +00:00
Sign in to join this conversation.
No description provided.