Error nginx 2.6.8
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, nginx
- Domain
- devops, infrastructure
Research direction
The report only identifies the 2.6.8 update and nginx bind() errors on port 80. Start by comparing the 2.6.8 Docker configuration with the previous release and reproducing the container startup; done means identifying the cause of the port conflict and confirming a working startup configuration.
Written by the indexing model from the issue text.
Description
Hello,
After the last update 2.6.8. I get the following error:
wallabag | 2024/01/11 13:18:17 [emerg] 153#153: still could not bind()
wallabag | nginx: [emerg] still could not bind()
wallabag | 2024/01/11 13:18:20 [emerg] 155#155: bind() to 0.0.0.0:80 failed (98: Address in use)
wallabag | nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address in use)
wallabag | 2024/01/11 13:18:20 [emerg] 155#155: bind() to [::]:80 failed (98: Address in use)
wallabag | nginx: [emerg] bind() to [::]:80 failed (98: Address in use)
wallabag | 2024/01/11 13:18:20 [emerg] 155#155: bind() to 0.0.0.0:80 failed (98: Address in use)
wallabag | nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address in use)
wallabag | 2024/01/11 13:18:20 [emerg] 155#155: bind() to [::]:80 failed (98: Address in use)
wallabag | nginx: [emerg] bind() to [::]:80 failed (98: Address in use)
- 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 3/5 1-2 days Newbie friendliness 57/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
Similar issues
-
Python Volcengine provider returns failures instead of raising themPossibly taken @Ricardo-M-L claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
agent-infra/sandbox#248 ·
-
chore priority:low size:S
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
celo-org/celopedia-skills#98 ·
Maintainers usually reply within 1 day
-
ready-for-pr
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
kunchenguid/firstmate#7679 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MISP/misp-docker#478 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
t4t5/omdrop-owl#83 ·