Works, but keeps restarting
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 5.1k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Remotely docker running on a synology with portainer stack
version: "3.9"
services:
remotely:
container_name: Remotely
image: immybot/remotely:latest
healthcheck:
test: timeout 10s bash -c ':> /dev/tcp/127.0.0.1/8080' || exit 1
interval: 10s
timeout: 5s
retries: 3
start_period: 90s
mem_limit: 4g
cpu_shares: 768
security_opt:
- no-new-privileges:false
restart: on-failure:5
ports:
- 5371:8080
volumes:
- /volume1/docker/remotely:/app/AppData:rw
environment:
- Remotely_ApplicationOptions__DbProvider=SQLite
- ASPNETCORE_ENVIRONMENT=Production
It was working flawlessly for the first couple of months, but now it is restarting by itself every 5 to 10 minutes.
A couple of key points from the log stand out:
Data Protection Warning: The log shows a warning about storing keys in /root/.aspnet/DataProtection-Keys, which might not persist across container restarts. This could/may be causing issues, as important configuration or session information may not be saved, leading to unexpected behavior or restarts.
How could this be happening on an installation that was previously working without issues and where no configuration has been tampered with? No new users, nothing— even the PowerShell scripts that were inserted are the same. 🤷♂️
Help ?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Docker/Portainer stack in the issue, including the healthcheck, restart policy, volume mapping, and environment settings. Review the container logs and health status to determine whether the container exits or fails its check; done means identifying the restart cause and documenting a reproducible configuration or diagnostic result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100