An electric motorcycle build kit appeals to riders seeking customization, cost savings, and hands-on learning by assembling or converting bikes to electric. It requires balancing this freedom with technical skill, safety, compatibility, and legal considerations to ensure reliable performance.
#ElectricMotorcycle
#BuildKit
#ourmotorcycleworld #wolink
https://www.ourmotorcycleworld.com/archives/2527
Most people know BuildKit as the thing that makes docker build fast. But BuildKit is a general-purpose build framework with a programmable architecture that can produce any artifact, not just container images. Here's how it works and how I used it to build Alpine APK packages.
BuildKit: Docker's Hidden Gem That Can Build Almost Anything
https://tuananh.net/2026/02/25/buildkit-docker-hidden-gem/
#HackerNews #BuildKit #Docker #HiddenGem #DevTools #Containerization
Most people know BuildKit as the thing that makes docker build fast. But BuildKit is a general-purpose build framework with a programmable architecture that can produce any artifact, not just container images. Here's how it works and how I used it to build Alpine APK packages.
Кэш-монтирование или Cache mount в Docker. Использование кэш-монтирования в GitLab CI/CD
Кэш-монтирование в Docker — это мощный инструмент, который может значительно ускорить процесс сборки образов в CI/CD. Но его правильная настройка в GitLab требует понимания не только работы BuildKit, но и особенностей взаимодействия с различными конфигурациями GitLab Runner — DinD и DooD. В этой статье я расскажу об устройстве кэш-монтирования в Docker и как его использовать в GitLab CI/CD. На примере простой сборки Python-проекта покажу готовые решения для кэширования зависимостей, чтобы оптимизировать сборку Docker-образов.
https://habr.com/ru/articles/995528/
#docker #deploy #gitlab #python #cache #dockerfile #cicd #dind #buildkit #git
#qemu is broken with latest #Alpine 3.23
https://gitlab.alpinelinux.org/alpine/aports/-/issues/17775
executing post-install
execve: No such file or directory
#arm #arm64 #crosscompiling #emulation #linuxEmulation #linux #github #gitlab #forgejo #codeberg #cicd #pipeline #pipelines #docker #containers #container #buildx #buildkit #docker_buildx #k8s #kubernetes #golang #controller #operator
Shipped BuildKit for RISC-V64. Green CI, packages built. Users tried it: crash loop.
"No worker found" - missing runc, wrong ENTRYPOINT/CMD, hanging tests.
Lessons:
✓ Test integration, not just compilation
✓ Add timeouts everywhere
✓ Document WHY, not just WHAT
Visible success hiding more profound problems. Post-deployment debugging is the real work.
#BuildKit #RISCV64 #Docker #DevOps #Debugging #PostDeployment #LessonsLearned #OpenSource #devEco
I shipped BuildKit for RISC-V64 two days ago. The workflows were green, packages built successfully, documentation looked thorough. Then users tried to actually use it. The container crash-looped immediately. "No worker found." Turns out "successful compilation" and "functional deployment" are very different things. The problems: - Missing runc binary meant OCI worker couldn't initialize (BuildKit needs at least one worker to run) - ENTRYPOINT/CMD split was wrong, so Docker Buildx was unable to pass runtime arguments - CI tests hung indefinitely when buildkitd tried to initialize workers without proper privileges - Cached GHCR credentials caused false "access denied" errors Three PRs later, the container works. But here's what I learned: - Testing individual components isn't enough. You need to test how components integrate with the systems that actually use them. It's not enough to verify the car starts; you need to verify it drives. - Always add timeouts. Even commands that "should never hang" will eventually hang. - Use your own packages consistently. Mixing Debian's runc 1.1.12 with our runc 1.3.0 builds created unnecessary version complexity. - Document the WHY, not just the WHAT. Explain when to use container images vs. APT packages. Users need context, not just instructions. The iceberg metaphor fits perfectly: visible success hiding more profound integration problems. Post-deployment debugging is where the real work happens. #BuildKit #RISCV64 #Docker #DevOps #Debugging #ContainerTechnology #LessonsLearned #PostDeployment #devEco
🔧 BuildKit for RISC-V64 in 4 Hours
Demo needed BuildKit for multi-platform builds. No RISC-V64 support in official image.
Built it myself:
✅ 0.26.2 compiled (pure Go)
✅ Debian + RPM packages
✅ Fixed dh_dwz for Go binaries
✅ Version filtering implemented
First Linux distro packages for BuildKit RISC-V64!
📦 https://bit.ly/4iKE20O
📖 https://bit.ly/4pSfKnW
#RISCV #Docker #BuildKit #DevOps #OpenSource #Linux #GoLang #devEco
Java/Mavenビルドが1秒に！Docker Multi-stage Build＋BuildKitで98%短縮した話
https://qiita.com/ntaka329/items/882e90d61671bdbd024f?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
So I've migrated a container build pipeline from (deprecated) #Kaniko to (shiny new) #BuildKit after reading documentation from #Gitlab on how to integrate image building in Gitlab CI/CD. Turns out the whole thing doesn't work without enabling privileged mode on the Gitlab runner. Judging from the discussion around the issue there is no tool except Kaniko that works without some sort of extended privileges.
ourmotorcycleworld
N-gated Hacker News
Hacker News
Habr
Eric Horwath
poddingue
Qiita - 人気の記事
Sebastian
GripNews