https://bllaude.github.io/tags/docker/Recent content in Docker on Brey Laude's websiteHugoenMon, 31 Aug 2026 17:01:53 +0800https://bllaude.github.io/article/wiring-codex-dockerized-omniroute/Mon, 31 Aug 2026 17:01:53 +0800https://bllaude.github.io/article/wiring-codex-dockerized-omniroute/<p>For anyone running Codex against multiple backends - official OpenAI, Kimi or DeepSeek endpoint, whatever happens to be cheapest or fastest that week - putting omniroute in front of it means Codex only ever needs to know about one base URL, while omniroute absorbs the churn of provider outages, rate limits, and credential rotation on the other side.</p>https://bllaude.github.io/article/deploying-omniroute-docker/Sat, 29 Aug 2026 16:32:11 +0800https://bllaude.github.io/article/deploying-omniroute-docker/<p>Running omniroute on Docker is the best default for me simply because I don’t want a global npm install polluting my host node environment, and it composes cleanly whether the box is a home server, a VPS, or my throwaway VM.</p>https://bllaude.github.io/article/kali-linux-docker-containers/Sun, 08 Jun 2025 18:46:01 +0800https://bllaude.github.io/article/kali-linux-docker-containers/<p>Kali Linux ships official OCI images under <code>kalilinux/kali-rolling</code>, <code>kalilinux/kali-last-release</code>, and <code>kalilinux/kali-bleeding-edge</code>. They are deliberately minimal, containing little beyond the base userland, so tooling is layered on top through Kali&rsquo;s metapackages. That makes them well suited to disposable, reproducible assessment environments on a remote server: you get a clean toolchain per engagement, isolated from the host and from each other, without maintaining a full Kali VM. Use them only against systems you are authorized to test.</p>