BLblago·Oct 14, 2020
In Dockerfile Security Best Practicesdocker
for-linux
Systems & Infrastructure2017–2025
docker / for-linux
for-linux
Docker Engine for Linux
17Distinct people
19Mentions
0Explicit recommenders
777GitHub stars
What to know before exploring
What it is
Docker Engine for Linux
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 7:02:50 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year19 dated mentions
Observed mentions: 2017-07-11 15:57:43 UTC to 2025-09-09 15:41:52 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 3 | 2 | 1 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 5 | 1 | 4 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 4 | 1 | 3 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
4 sourceslink for the missing DOCKER-USER chain: https://github.com/docker/for-linux/issues/810 - so if you are unlucky you are one apt upgrade away from data theft...
In New ‘Meow’ attack has deleted almost 4k unsecured databasesIt's also easy to get bitten by Docker. You can secure your server with iptables/ufw only to discover that docker happily punches through your firewall and you need to filter on the DOCKER-USER chain - and even that was broken: https://unrouted.io/2017/08/15/docker-firewall/ https://github.com/docker/for-linux/issues/690
In New ‘Meow’ attack has deleted almost 4k unsecured databasesAsk HN: Is Docker to blame for recent security breaches?
I'm assuming a lot here, but I believe many recent data breaches are due to some company leaving their servers wide open. I'm assuming a lot here, but its reasonable that most deployments today are containerized, and if not Kubernetes, they're usually docker.
Are most developers aware that "ufw default deny incoming" does not work unless using host networking, or unless we modify the docker daemon or IP tables directly?
Also, with the simplicity of ufw, do folks take the time to learn how to work with ip tables? I was bitten by this twice when hosting small dev stuff like mongodb, redis and nfs - often accessed in trusted networks without authentication - where after locking down ufw I'd get a notice from the cloud provider (DO, Hetzner) a few days later telling me which port I had open. After debugging and ending up here (https://github.
Read the rest
com/docker/for-linux/issues/690). First time I made a mental note. Second time I finally wrote it down. Its really not obvious.
If you host on your own infrastructure, or AWS, I don't think you get a notice, so docker-compose up can be really dangerous.
I guess I would like your comments on whether this is a probable cause of many breaches and whether there is some responsibility (technical, not legal) on docker to properly document this behavior and probably fix.