Selfhosted

46677 readers

1188 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 2 years ago

MODERATORS

[email protected]

Restarting Docker containers that never started successfully (lemmy.ml)

submitted 8 months ago by [email protected] to c/[email protected]

6 comments fedilink hide all child comments

I have some of my Docker containers bind to Tailscale IPs on the host. Even though I edited the Docker service to depend on tailscaled.service and it starts about 10 seconds after it, every once in a while Tailscale interface won't be ready by the time the containers try to spin up after a reboot.

Since restart policies do not apply to containers that has never started and ran at least for a while, Docker gives me no choice but to restart either those containers or the Docker daemon manually.

Is there a way to have Docker daemon try to restart containers even though they failed on the first try?

A restart policy only takes effect after a container starts successfully. In this case, starting successfully means that the container is up for at least 10 seconds and Docker has started monitoring it. This prevents a container which doesn't start at all from going into a restart loop.

https://docs.docker.com/engine/containers/start-containers-automatically

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 8 points 8 months ago* (last edited 8 months ago) (1 children)

Delay the start of your containers with the tailscale dependency. Are you using required or depends_on in your docker-compose.yml

https://hatchjs.com/docker-compose-conditionally-start-service/

If you're using kubernetes you can make the requirements at the pod level

https://stackoverflow.com/questions/69423932/container-initialization-order-in-pod-on-k8s

Edit: If using docker-compose.yml you can set a condition on a healthcheck

You can also specify a condition that must be met before the service is started. For example, the following configuration will start the web service only if the db service is healthy:

version: ‘3.7’
services:
web:
image: nginx
depends_on:
– db
condition: service_healthy

The service_healthy condition checks the health of the db service using the docker-compose ps command. If the db service is healthy, the web service will be started.