pack
buildah
Our great sponsors
pack | buildah | |
---|---|---|
46 | 25 | |
2,373 | 6,918 | |
2.0% | 1.8% | |
9.5 | 9.6 | |
2 days ago | 7 days ago | |
Go | Go | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pack
- Différentes façons de déployer une application front faites en JS
-
K8s powered Git push deployments
I've recently found this quote by Kelsey Hightower:
"I'm convinced the majority of people managing infrastructure just want a PaaS. The only requirement: it has to be built by them."
Source: https://twitter.com/kelseyhightower/status/85193508753294540...
In the last few weeks, I've experimented a bit with Flux (https://fluxcd.io/), Tekton (https://tekton.dev/) and Cloud Native Buildpacks (https://buildpacks.io/) on how to provide K8s powered git push deployments without using a dedicated CI/CD server.
My project is still in early alpha stage and just a proof of concept :-) My vision is to expand it into an Open Source PaaS in the future.
Do you think the above quote is true? What does an open source PaaS need to be like in order to be accepted by software developers?
Some other projects have been discontinued in the past (like Flynn or Deis) or were created before the Kubernetes era.
Is it the right direction to provide a Heroku like solution based on K8s or is it better to provide an Open Source Infrastructure as Code library with building blocks to avoid everything from scratch?
-
Crafting container images without Dockerfiles
Although Dockerfiles have the benefit of migrating existing workloads to containers without having to update your toolchain, I definitely prefer the container-first workflow. Cloud Native [Buildpacks](https://buildpacks.io/) are a CNCF incubating project but were proven at Heroku. Buildpacks support common languages, but working on a Go project I've also had a great experience with [ko](https://ko.build/). Free yourself from Dockerfile!
-
Kubero : alternative à Heroku pour Kubernetes …
Cloud Native Buildpacks
-
The world outside of WordPress
It's big and overwhelming and sometimes scary. But you know what? It's also fun, engaging, and very refreshing. Because I'm a DevRel, I don't have many chances to focus on something particular. Still, I'm having a lot of fun exploring different CMSs (like Statamic, Craft, or Sanity), new approaches (at last, I understood why the headless approach is so important), and diving into tech I never used before (hello Buildpacks).
- Does anyone use any alternatives to Dockerfile for creating containers? Something with nicer syntax?
- Jetstack Paranoia: A New Open-Source Tool for Container Image Security
-
YAML Buildpack: Auto Validate Configuration Repositories
[5] https://buildpacks.io/
-
Devbox 📦 : Instant, easy, and predictable shells and containers
Devbox analyzes your source code and instantly turns it into an OCI-compliant image that can be deployed to any cloud. The image is optimized for speed, size, security and caching ... and without needing to write a Dockerfile. And unlike buildpacks, it does it quickly.
-
A selfhosted Heroku clone on your Kubernetes cluster
I had a short look into buildpacks.io . So I don't have a firm opinion yet. But as much i understand now, it really builds Container images. Kubero goes a different approach. The buildstep only compiles the project to a mounted volume, which is mounted readonly to the running container. Further more is the detection step unnecessary, since the dev knows what he wants to build and selects the buildimage. How ever, I'm still looking into it, so see if my project can profit from the great work there in any other way.
buildah
-
A gopher’s journey to the center of container images
For the task of building the graph image, my first idea was to rely on buildah. In fact, our design was already heavily relying on containers/image for all things regarding copying images from one registry to the other, or from one registry to an archive. The obvious choice was to use the same suite of modules in order to keep dependencies to a minimum.
-
How to use Podman inside of a container
You do realize that, under the hood, buildah uses a container engine (runc by default)? See https://github.com/containers/buildah/blob/main/docs/buildah...
-
Container and image vocabulary
buildah
-
From code to customers in just 13 seconds.
# https://github.com/containers/buildah/issues/3666 volume /var/lib/containers
-
Podman v4.4, Buildah v1.29 released!
Last week, Buildah version 1.29 was also released. The prune command has been added to clean intermediate images as well as the build and mount cache. Support for the –group-add option to the from and build commands was added. One useful feature of this, it to use the –group-add keep-groups option, which allows rootless users to take advantage of their group access to file and devices mounted into the build containers. And the –cache-from and –cache-to options for the build command now allow for multiple sources. This can be used to improve the speed of builds, especially in CI/CD environments.
- Crafting container images without Dockerfiles
-
Rails on Docker · Fly
Unfortunately this syntax is not generally supported yet - it's only supported with the buildkit backend and only landed in the 1.3 "labs" release. It was moved to stable in early 2022 (see https://github.com/moby/buildkit/issues/2574), so that seems to be better, but I think may still require a syntax directive to enable.
Many other dockerfile build tools still don't support it, e.g. buildah (see https://github.com/containers/buildah/issues/3474)
Useful now if you have control over the environment your images are being built in, but I'm excited to the future where it's commonplace!
-
Container Deep Dive 2: Container Engines
For more information regarding the bundled tools see: CRI tools.
-
Does anyone use any alternatives to Dockerfile for creating containers? Something with nicer syntax?
You can use buildah and basically use any language you want, most easy solution would be bash. https://github.com/containers/buildah
What are some alternatives?
kaniko - Build Container Images In Kubernetes
buildkit - concurrent, cache-efficient, and Dockerfile-agnostic builder toolkit
rules_docker - Rules for building and handling Docker images with Bazel
helm-charts - Prometheus community Helm charts
jib - 🏗 Build container images for your Java applications.
coolify - An open-source & self-hostable Heroku / Netlify / Vercel alternative.
SSVM - WasmEdge is a lightweight, high-performance, and extensible WebAssembly runtime for cloud native, edge, and decentralized applications. It powers serverless apps, embedded functions, microservices, smart contracts, and IoT devices.
podman - Podman: A tool for managing OCI containers and pods.
okteto - Develop your applications directly in your Kubernetes Cluster
go-admin - 基于Gin + Vue + Element UI & Arco Design & Ant Design 的前后端分离权限管理系统脚手架(包含了:多租户的支持,基础用户管理功能,jwt鉴权,代码生成器,RBAC资源控制,表单构建,定时任务等)3分钟构建自己的中后台项目;项目文档》:https://www.go-admin.pro V2 Demo: https://vue2.go-admin.dev V3 Demo: https://vue3.go-admin.dev Antd 订阅版:https://antd.go-admin.pro
terraform-provider-azurerm - Terraform provider for Azure Resource Manager