3 ms·
One unfortunate thing about Docker that exacerbates this is that certain places where you can specify a local container, if the container can’t be found (e.g. a
by paulgb 4y ago
One unfortunate thing about Docker that exacerbates this is that certain places where you can specify a local container, if the container can’t be found (e.g. a typo), Docker will automatically attempt to pull it from dockerhub. IIRC “docker run” has this behavior.
So even if you’re used to double-checking container names before you pull them, you have to be vigilant even when using locally-built containers.
- diarrhea 4y agoMuch like subdomains, you could use a namespace you control for all local work as well. Name all your images “yourname/actualimagename”. At worst, you pull in an image of yours from remote. The analogy comes from local subdomains. Use “home.yourname.com” and your dns server can be set to never look this up in upstream servers and resolve it locally. No accidental leakage anymore.