むー。docker build = buildkit経由がデフォルトになって・・・。podmanバックエンドとは相性悪くなってる。 DOCKER_BUILDKIT=0つけるかpodmanコマンドに移行するなりしろってことかー。

This article explains that BuildKit is not just Docker’s build engine but a general-purpose framework that can turn custom frontend definitions into images, tarballs, local artifacts, and package outputs ➤ ku.bz/mLZp6ZLys

Dockerfile Best Practices: From Base Images and Caching to SBOM, Cosign, and CI/CD Join my Telegram channel for exclusive content: t.me/rootacessacademy A set of best practices: not every point is needed for every project, but almost every point eventually comes up during a code review, in CI, or after an unpleasant incident. Covers all levels: from basic mistakes like `COPY . .`, using the `latest` tag, and running as root, to production-grade topics like BuildKit, secrets management, SBOMs, image signing, and software supply chain security. That's why the tone here is intentionally dry, direct, and engineering-focused: no long intros, no fluff, and no rehashing documentation just for the sake of it. — This is a working cheat sheet to refer back to when writing, reviewing, or refining a Dockerfile. ⏺ Link to the full article: habr.com/ru/articles/1041784… #Docker #Kubernetes #Containers #DevOps #DevSecOps #Admin #Linux

BuildKit. A curated shop for creator tools — Notion systems, templates, AI prompts, spreadsheets. Everything you need to actually work.

tried to promote a new Dockerfile linter with buildkit capabilities and the first issue was massively rejected. People are so afraid of security attacks nowadays. Only big packages could do that

Container Image Building with BuildKit giantswarm.io/blog/container…

Every developer tool today is "you do the work, AI helps." The next generation is "AI does the work, you review." Built BuildKit — an autonomous agent that ships code while you sleep.

🧡 New Opengrep release is here: v1.22.0 Highlights: • More Dockerfile support improvements, including legacy syntax and BuildKit extensions • Better support for Go interfaces

We were burning CPU, RAM, and ~10GB of disk on our VPS every deploy — building a large Next.js app directly on the server. So we changed the model: Build on GitHub Actions → push to GHCR → Dokploy pulls and runs. No more yarn build on production. Deploys went from 15–20 minutes (when they didn’t fail) to seconds. What changed: → Server = run containers, not compile code → Same image from staging (:release) to prod (:production) → Rollbacks = pull a previous tag → Freed ~10GB from old BuildKit cache alone Same app. Cleaner ops. If your VPS is still building Docker images on every push, you might not need a bigger server — you might need a different pipeline. Build on GitHub, Deploy with a Pull gamms.app/home/CWXMGLQU

I FIND A BETTER WAY DEPLOYING NEXTJS APP ON MY VPS. We were burning CPU, RAM, and ~10GB of disk on our VPS every deploy building a large Next.js app directly on the server. So we changed the model: Build on GitHub Actions → push to GHCR → Dokploy pulls and runs. No more yarn build on production. Deploys went from 15–20 minutes (when they didn’t fail) to seconds. What changed: → Server = run containers, not compile code → Same image from staging (:release) to prod (:production) → Rollbacks = pull a previous tag → Freed ~10GB from old BuildKit cache alone Same app. Cleaner ops. If your VPS is still building Docker images on every push, you might not need a bigger server — you might need a different pipeline.

Abis beli VPS, kepikiran menghambur2kan token yang dimiliki. Jadilah PaaS kecil2an, pakai linux runtime, no docker dockeran (cuma minjem buildkit nya aja). #PamerAjaDulu

just shipped buildkit secrets support to the zEnv cli your zenv secrets will now work natively in docker builds

avikmukherjee.com/blog/how-n… On sunday itself wrote this blog. So was creating vercel clone if you remember so in there I used nixpacks and buildkit as required. So wanted to have summary for them and it was this blog.

New #Docker SadServers scenario "Tallinn": BuildKit & Docker build mismatch - practice troubleshooting a broken CI/CD on a live server (inspired by a real issue we had 😄)

Kamino is becoming the AWS of onchain credit on Solana. @xplaceapp just launched Credit Mode. Borrow against your crypto, spend the liquidity, keep your exposure, earn yield. powered by Kamino. why @kamino specifically? Battle tested. isolated markets that ring-fence risk per pool and a Buildkit SDK that lets any app embed lending without building from scratch. XPlace joins @privy, @OneKeyHQ, and @MarinadeFinance in choosing Kamino as their lending backend. The user never needs to visit Kamino. They just use an app that runs on Kamino to borrow, spend, and earn all on @solana

🐳 After giving my @Docker Bake talks at several conferences, I turned it into an article series. Part 1 is live: declarative parallel multi-image Docker builds with Bake ⚡ Article repo 👇 #Docker #DevOps #BuildKit #DockerBake #GoogleCloud @GoogleCloudTech

On episode 51 of The Kubelist Podcast, Kyle Galbraith (@kylegalbraith) shares the story behind @depotdev and explains how the company evolved from accelerating Docker builds into building an entirely new CI platform designed for the AI era. The conversation explores BuildKit internals, remote caching, microVMs, AWS infrastructure, and why modern software development may require rethinking CI from the ground up. Tune in! @readkubelist @shipyardbuild @replicatedhq hubs.ly/Q04gWtmX0

If I had to master Docker, I’d learn these concepts: 1. What is Docker 2. Containers vs Virtual Machines 3. Docker Architecture 4. Docker Engine 5. Docker CLI 6. Docker Desktop 7. Docker Images 8. Docker Containers 9. Docker Hub 10. Container Lifecycle 11. Pulling Images 12. Building Images 13. Dockerfile Basics 14. Dockerfile Instructions 15. Layers & Caching 16. Multi-Stage Builds 17. Base Images 18. Alpine Images 19. Image Optimization 20. Container Networking 21. Bridge Network 22. Host Network 23. Overlay Network 24. Port Mapping 25. Volumes 26. Bind Mounts 27. Persistent Storage 28. Environment Variables 29. Secrets Management 30. Docker Compose 31. Multi-Container Applications 32. Service Dependencies 33. Health Checks 34. Restart Policies 35. Logging Drivers 36. Monitoring Containers 37. Docker Logs 38. Resource Limits 39. CPU & Memory Allocation 40. Container Security 41. Linux Namespaces 42. Control Groups (cgroups) 43. Docker Registry 44. Private Registries 45. Image Tagging 46. Versioning Strategies 47. CI/CD with Docker 48. Docker in GitHub Actions 49. Docker in Jenkins 50. Docker in GitLab CI 51. Container Orchestration 52. Docker Swarm 53. Kubernetes Basics 54. Running Docker on Cloud 55. Docker on AWS 56. Docker on Azure 57. Docker on GCP 58. Reverse Proxy with Nginx 59. Load Balancing 60. Service Discovery 61. Scaling Containers 62. Stateful vs Stateless Containers 63. Database Containers 64. Redis Containers 65. PostgreSQL Containers 66. MySQL Containers 67. MongoDB Containers 68. Debugging Containers 69. Inspecting Containers 70. Exec into Containers 71. Networking Troubleshooting 72. Image Scanning 73. Vulnerability Management 74. DevSecOps with Docker 75. Rootless Containers 76. Distroless Images 77. Docker Best Practices 78. Layer Minimization 79. Build Optimization 80. Caching Strategies 81. Backup & Restore 82. Multi-Architecture Images 83. ARM vs x86 Containers 84. Docker APIs 85. Container Runtime 86. OCI Standards 87. Podman vs Docker 88. BuildKit 89. Docker Extensions 90. AI Workloads in Docker 91. Microservices with Docker 92. Event-Driven Systems 93. Observability 94. Prometheus & Grafana 95. ELK Stack with Docker 96. High Availability 97. Fault Tolerance 98. Production Deployment (...and more concepts) === 👋 PS - Want a complete Docker roadmap from beginner to advanced? Read right now: → Docker Ebook: codewithdhanian.gumroad.com/… === 💾 Save this for later & RT to help others learn Docker. 👤 Follow @e_opore turn on notifications.

Day 11 — DevOps Debugging Masterclass 30-minute CI pipeline = developer productivity killer. Where time actually goes: 1. Dependency install — cache this! 2. Docker builds without layer cache 3. Sequential jobs that could run in parallel 4. Test suite with no parallelism 5. Pulling large base images every run Quick wins: • Cache node_modules keyed to lockfile hash • Use --cache-from in Docker builds • Split unit vs integration tests, run parallel • Use remote build cache (Depot, BuildKit) • Profile with pipeline trace timings Goal: under 5 minutes for PR feedback. Speed of CI = speed of iteration.