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'm using the below docker-compose to run fedifetcher however I've noticed that it's constantly running, ending and running again within minutes (or even seconds) as per the below screenshot from my Healthchecks instance. It seems that it's not picking up the delay in the restart_policy but I'm not sure why?
services:
fedifetcher:
container_name: fedifetcher
stdin_open: true
tty: true
image: ghcr.io/nanos/fedifetcher:latest
command: "--access-token=${TOKEN} --server=${SERVER} --config=/app/artifacts/config.json"
# Persist our data
volumes:
- /opt/fedifetcher/:/app/artifacts
# Use the `deploy` option to enable `restart_policy`
deploy:
# Don't go above 1 replica to avoid multiple overlapping executions of the script
replicas: 1
restart_policy:
# The `any` condition means even after successful runs, we'll restart the script
condition: any
# Specify how often the script should run - for example; after 1 hour.
delay: 1h
The text was updated successfully, but these errors were encountered:
It seems docker compose ignores the delay command, it only works when deployed as a swarm/stack. I apologise I didn't see this, in my limited testing I thought I had it working.
I 'solved' it by creating my own entrypoint in the compose file and adding a basic unix sleep command like below.
cc'ing @benyafai
I'm using the below docker-compose to run fedifetcher however I've noticed that it's constantly running, ending and running again within minutes (or even seconds) as per the below screenshot from my Healthchecks instance. It seems that it's not picking up the delay in the restart_policy but I'm not sure why?
The text was updated successfully, but these errors were encountered: