- Community aggregator
- Country: United States
Docker
Built to run on trust, for the agentic era Discussion | Link
Built to run on trust, for the agentic era Discussion | Link
New Docker. New whale. New mission. 🐳 On November 19, 2026, Docker introduced its new brand identity, including a redesigned logo, a new color palette, and a bigger strategic ambition. You can check the official brand guidelines here: Docker brand guidelines . Docker also revamped the whole…
Password managers hold the keys to everything you own online, yet the hosted ones put that vault on someone else's servers and often lock useful features behind a subscription. If you'd rather keep control of your own data, self-hosting is a realistic option, even on a small VPS. In this guide we…
When you publish a container port, the engine inserts its own packet-filter rules ahead of the host firewall. A bind that looks locked down in UFW or firewalld can still be reachable from the network. The usual surprises are a Compose file that publishes 5432:5432 on every interface, a service…
If someone builds or hosts your website or web app, ask them one question this week: do we publish any public container images, and are our passwords and keys kept out of them? New research shows that keys left inside public Docker Hub images can be found and used in seconds, not days. What…
You flip on output: "standalone" to shrink the Docker image, the container starts, the HTML arrives — and the page is completely unstyled. Every /_next/static/css/....css and /_next/static/chunks/....js request 404s, while next dev on your laptop looks perfect. Later, images start returning 500…
I fixed a typo in a README. One character. Then I ran docker build and watched it reinstall every package in my package-lock.json from scratch, which took about a minute and a half. I hadn't touched package.json and I hadn't touched the lockfile. Docker re-ran npm ci on every build anyway, and for…
Originally published on proxymint . Docker proxy settings live in three places: daemon.json for pulls, build args for builds, config.json for containers. Tested traps, leaks and fixes. TL;DR Your shell's HTTPS_PROXY does nothing for docker pull. The daemon does the pull, so the proxy goes in…