Docker container stuck in restart loop on first-time docker-compose up
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker, docker-compose
- Domain
- devops, infrastructure
Research direction
Start with the default docker-compose.yml, then reproduce using docker-compose up -d and inspect docker-compose logs -f wallabag. Compare the wallabag startup and mysql readiness behavior. Done means the first-time startup becomes healthy reliably, or reports a clear dependency failure instead of restarting indefinitely.
Written by the indexing model from the issue text.
Description
Describe the bug
When running docker-compose up for the first time using the default docker-compose.yml, the wallabag container enters a restart loop and never becomes healthy.
To Reproduce
Steps to reproduce the behavior:
- Clone the repo
- Run
docker-compose up -d - Check
docker psand logs:docker-compose logs -f wallabag
Logs Snippet
wallabag_1 | Migrating database...
wallabag_1 | Doctrine\DBAL\Exception\ConnectionException: An exception occurred in driver: SQLSTATE[HY000] [2002] Connection refused
wallabag_1 | Retrying in 5 seconds...
Expected behavior
The container should wait until the mysql container is ready or fail with a clearer error if dependencies aren't available.
Environment
- OS: Ubuntu 22.04
- Docker: 24.0.2
- Docker Compose: 2.18.1
- Branch: main
- Wallabag Version: latest
Workaround
Manually restarting the container after 30 seconds works, but not ideal for CI/CD.
Let me know if you want a second one with a different issue (e.g., volume persistence or networking).
- Dominant language
- Shell
- Stars
- 771
- Forks
- 168
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
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.
More from wallabag/docker
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Awaiting response
Difficulty 4/5 3-5 days Newbie friendliness 32/100
-
Difficulty 4/5 3-5 days Newbie friendliness 28/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Similar issues
-
data only (no code) good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
upstream-release
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LinkStackOrg/linkstack-docker#170 · 8 reactions ·
-
Negative subscript on a sparse array counts from the number of elements, not from the highest indexOpenarea: compat bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
reubeno/brush#1570 · 1 comment ·
Maintainers usually reply within 1 day