this post was submitted on 30 Jun 2023
3 points (80.0% liked)

Selfhosted

40198 readers
569 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
HybridSarcasm@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
3
How to trigger a container restart based on successful update/image change of another container? (lemmy.world)
submitted 1 year ago by gobbling871@lemmy.world to c/selfhosted@lemmy.world
12 comments fedilink hide all child comments
 

Basically have watchtower monitor and update containers whenever new images are released. I've recently noticed that with searxng (using redis as db), hosted through nginx proxy manager, will have a steady downtime of about 15mins post update then come back online.

This is extremely frequent for searxng's case as I have watchtower run every day and my preferred way of running most of my containers is with the latest tag. The way out of this downtime in my experience is a restart of NPM which brings back the searxng service.

I'm looking for a way to automate a restart of the NPM container after a successful update of searxng's container.

I have checked the docs for watchtower, and the lifecycle hooks (a way to run sh scripts pre/post update) are able to run only from the applied container and not from the host system.

you are viewing a single comment's thread
view the rest of the comments
[–] gobbling871@lemmy.world 0 points 1 year ago

No worries. I ended up writing a systemd service that restarts the npm container a minute after the watchtower runs. I don't know why I didn't think of that earlier but I guess it's a much simpler solution than using depends_on with npm which hosts a lot of my other services.