Error in 'blog' demo --- can't open blog.py
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker, docker-compose, python
- Domain
- devops, infrastructure
Research direction
Start in demos/blog and reproduce the failure with docker-compose up, then compare the iptables error with the linked Moby issue. Determine whether the failure belongs to the demo configuration or the host Docker/iptables setup; done means the cause and a reproducible project-level fix are established, or the issue is documented as environmental.
Written by the indexing model from the issue text.
Description
I'm unable to build the 'blog' demo application using docker-compose up. I'm definitely not a docker expert, so it could just be an easy fix.
I try to run docker-compose up in the demos/blog directory, but the build fails because of an unknown option for the iptables command during postgres configuration ( docker0: iptables v1.8.4 (legacy): unknown option "--\dport" ).
Below is the full output from docker-compose up:
[robertc@Z38S blog]$ docker-compose up
Starting blog_postgres_1 ...
WARNING: Host is already in use by another container
ERROR: for blog_postgres_1 Cannot start service postgres: driver failed programming external connectivity on endpoint blog_postgres_1 (7fc11caf4be5a390d6ccdced928c5ea11d1768090d32b3b0709d41e\
d571e00bd): (iptables failed: iptables --wait -t nat -A DOCKER -p tcp -d 0/0 --dport 32797 -j DNAT --to-destination 172.17.0.2:3306 ! -i docker0: iptables v1.8.4 (legacy): unknown option "--\
dport"
Try `iptables -h' or 'iptables --help' for more information.
(exit status 2))
ERROR: for postgres Cannot start service postgres: driver failed programming external connectivity on endpoint blog_postgres_1 (7fc11caf4be5a390d6ccdced928c5ea11d1768090d32b3b0709d41ed571e00\
bd): (iptables failed: iptables --wait -t nat -A DOCKER -p tcp -d 0/0 --dport 32797 -j DNAT --to-destination 172.17.0.2:3306 ! -i docker0: iptables v1.8.4 (legacy): unknown option "--dport"
Try `iptables -h' or 'iptables --help' for more information.
(exit status 2))
ERROR: Encountered errors while bringing up the project.
Edit: This could be related to this issue. I'll check to see if the suggested fix (symlink iptables-nft) works later today.
- Dominant language
- Python
- Stars
- 22.2k
- Forks
- 5.6k
- Avg merge
- 3h 42m
- Merged PRs (30d)
- 16
Contributor 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 tornadoweb/tornado
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
tornadoweb/tornado#3701 · 1 comment ·
-
httpserver
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
tornadoweb/tornado#1050 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
tornadoweb/tornado#3728 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 64/100
tornadoweb/tornado#3651 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 50/100
tornadoweb/tornado#3616 · 2 comments ·
All issues in tornadoweb/tornado
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100