-
Notifications
You must be signed in to change notification settings - Fork 7.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updates for moby 28.0.1 #22086
Updates for moby 28.0.1 #22086
Conversation
Signed-off-by: Rob Murray <rob.murray@docker.com>
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Signed-off-by: Rob Murray <rob.murray@docker.com>
Signed-off-by: Rob Murray <rob.murray@docker.com>
69cc8ea
to
0a94868
Compare
Just a quick check, because I tend to zone out on iptables rules 😂 - with the rewrite, the docs are still usable for those who didn't update to v28.0.0 / v28.0.1, or is there a differentiation we need to make ("if you're running < v28.0, then ....")? I know we try to keep our docs reflect "current version" in most cases, but just in case it's relevant for people who are not yet on latest. |
I think it's ok ... in the third commit I left in the warning about remote access to ports published to 127.0.0.1 ("In releases older than 28.0.0 ..."). And, in the second commit I noted the change in setting the FORWARD policy to DROP (with another "In releases older than 28.0.0, ..." warning). |
☝️ to prevent accidental merge; I think these docs changes should go in after we did the v28.0.1 release, so don't merge yet until we did to prevent confusion 😅 |
Description
DOCKER-FORWARD
, which splits Docker's rules out of the mainFORWARD
chain where they were being antisocial - related to Add chain DOCKER-FORWARD moby/moby#49518Related issues or tickets
Reviews