You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am thinking of adding image names to .env, some for x86_64, some (commented out) for aarch64.
I had problems once when restarting the "web" container only, I suspect I might have introduced a "race condition" of some sorts. Icinga couldn't start anymore. I haven't verified it again after I moved the director config into a seperate file, executed only once. I suspect this might have been the culprit.
All my docker builds were done from scratch... I also always deleted the volumes and local directories (but not the builder cache!). Surprisingly on an RPi4 - with an micro SD, not some SAN/NAS backend. I am eating my own dog food and actually have that running live... :-)
So long :-)
Tom
The text was updated successfully, but these errors were encountered:
Thank you Tom! I have just accepted your pull request and merged with the main branch. TBH, I am not a fan of director, but it's good to have it in the build.
Good for the image names, I have never really considered different architectures as we run Icinga2 on cloud.
Hi,
I am thinking of adding image names to .env, some for x86_64, some (commented out) for aarch64.
I had problems once when restarting the "web" container only, I suspect I might have introduced a "race condition" of some sorts. Icinga couldn't start anymore. I haven't verified it again after I moved the director config into a seperate file, executed only once. I suspect this might have been the culprit.
All my docker builds were done from scratch... I also always deleted the volumes and local directories (but not the builder cache!). Surprisingly on an RPi4 - with an micro SD, not some SAN/NAS backend. I am eating my own dog food and actually have that running live... :-)
So long :-)
Tom
The text was updated successfully, but these errors were encountered: