Live data from Hacker News

The Ultimate Docker Cheat Sheet

devopscycle.com

1–10 of 27 posts

Re: The Ultimate Docker Cheat Sheet

#3
This looks useful, I wish I'd found it a month ago. One suggestion: could we have a more printer-friendly version (ie, without large patches of colour and without large patches of black)?

Re: The Ultimate Docker Cheat Sheet

#5
post #3

This looks useful, I wish I'd found it a month ago. One suggestion: could we have a more printer-friendly version (ie, without large patches of colour and without large patches of black)?

That is actually a great idea. I will bring this up in my team.

Re: The Ultimate Docker Cheat Sheet

#6
I think Docker has a fairly well designed CLI and I don't find myself having to Google commands for it often. It follows a few pretty consistent patterns that I wish git had tried to stick with rather than the concoction of words and flags for common actions it ended up with.

Re: The Ultimate Docker Cheat Sheet

#7
Please add

- Security warnings:

like: Note that ports which are not bound to the host (i.e., -p 5432:5432 instead of -p 127.0.0.1:5432:5432) will be accessible from the outside. This also applies if you configured UFW to block this specific port, as Docker manages its own iptables rules. https://docs.docker.com/network/packet-filtering-firewalls/

- using trivy scanner: "trivy image --ignore-unfixed ... "

---------------------

Why the security is important?

- https://sysdig.com/blog/zoom-into-kinsing-kdevtmpfsi/ : "Some of those Docker engines weren’t configured with authentication, which make them a perfect target for Kinsing attacks."

- https://sysdig.com/blog/cloud-defense-in-depth/ ( JULY 4, 2023: Cloud Defense in Depth: Lessons from the Kinsing Malware )

- https://thenewstack.io/kinsing-malware-targets-kubernetes/ ( Jan 13th, 2023 , Kinsing Malware Targets Kubernetes )

- https://stackoverflow.com/search?q=kinsing

Re: The Ultimate Docker Cheat Sheet

#8
post #7

Please add - Security warnings: like: Note that ports which are not bound to the host (i.e., -p 5432:5432 instead of -p 127.0.0.1:5432:5432) will be accessible from the outside. This also applies if you configured UFW to block this specific port, as Docker manages its own iptables rules. https://docs.docker.com/network/packet-filtering-firewalls/ - using trivy scanner: "trivy image --ignore-unfixed ... " ------------…

Author here. This is actually a good point, we will add this in the near future. Thanks for your input.
Post reply on HN