wagi
distroless
Our great sponsors
wagi | distroless | |
---|---|---|
14 | 122 | |
867 | 17,695 | |
1.3% | 2.1% | |
1.8 | 9.3 | |
almost 2 years ago | 7 days ago | |
Rust | Starlark | |
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.
wagi
-
Reminiscing CGI Scripts
WAGI and WCGI are the WASM based spiritual successors.
https://github.com/deislabs/wagi
https://wasmer.io/posts/announcing-wcgi
-
A simple web server written in Awk
Compile a CGI program in any language to WASI, then use https://github.com/deislabs/wagi to run it.
-
Running WASI binaries from your HTML using Web Components
Yeah of course! They've got STDIN/STDOUT/STDERR and I've built a Virtual Filesystem. But if you're using WASI binaries locally they don't have that restriction.
You might be interested in WAGI: https://github.com/deislabs/wagi
And to catch up on WASI: https://xeiaso.net/talks/unix-philosophy-logical-extreme-was...
-
Waggy, the library for writing WAGI API handlers in Go
As I'm sure you've heard, WASM has been growing in popularity and use over the past few years. And with the creation of WASI (Web Assembly System Interface) and WAGI (Web Assembly Gateway Interface), WASM is starting to venture outside of running just in the browser. And in the case of WAGI, if you've been programming since the earlier days of the internet, it might feel very similar to CGI programming (and that's because it's based on CGI1.1!) WAGI provides a way for developers to define handlers for HTTP requests and route them to specific functions inside of, or entire, WASM modules. It does so by piping the headers of the incoming request to os.Args[1:], piping the body of the incoming request to os.Stdin, and writing the response to os.Stdout. (To learn more about configuring, routing, compiling, and deploying WAGI routes, as well as the limitations of WAGI routes, please consult the WAGI docs and the TinyGo WASM docs)
-
Rethinking Virtualization for Back Ends
What do you think of WAGI [1], which is basically CGI for WASM modules.
[1]: https://github.com/deislabs/wagi/blob/main/docs/writing_modu...
- Isolates, MicroVMs, and WebAssembly (In 2022)
-
The Promise of WASM
as serverless functions (https://github.com/deislabs/wagi)
-
Single Page Applications using Rust (with WASM)
I'm experimenting with WASM & Rust but with a different framework named wagi, there's a great video by Rainer Stropek & Stefan Baumgartner that gives a little introduction to it [0]
[0]: https://www.youtube.com/watch?v=9NDwHBjLlhQ
[1]: https://github.com/deislabs/wagi
-
Building a WebAssembly-powered serverless platform
Krustlet and WAGI are two such projects.
-
Introduction to Hippo: The WebAssembly PaaS
It does support it, the runtime we are currently using enables that -- see https://github.com/deislabs/wagi/blob/main/docs/writing_modu...
Good point on the docs, I will open an issue and add some information about it, thanks!
distroless
-
Chainguard Images now available on Docker Hub
lots of questions here regarding what this product is. I guess i can provide some information for the context, from a perspective of an outside contributor.
Chainguard Images is a set of hardened container images.
They were built by the original team that brought you Google's Distroless (https://github.com/GoogleContainerTools/distroless)
However, there were few problems with Distroless:
1. distroless were based on Debian - which in turn, limited to Debian's release cadence for fixing CVE.
2. distroless is using bazelbuild, which is not exactly easy to contrib, customize, etc...
3. distroless images are hard to extend.
Chainguard built a new "undistro" OS for container workload, named Wolfi, using their OSS projects like melange (for packaging pkgs) and apko (for building images).
The idea is (from my understanding) is that
1. You don't have to rely on upstream to cut a release. Chainguard will be doing that, with lots of automation & guardrails in placed. This allow them to fix vulnerabilties extremely fast.
- Language focused Docker images, minus the operating system
-
Using Alpine can make Python Docker builds 50× slower
> If you have one image based on Ubuntu in your stack, you may as well base them all on Ubuntu, because you only need to download (and store!) the common base image once
This is only true if your infrastructure is static. If your infrastructure is highly elastic, image size has an impact on your time to scale up.
Of course, there are better choices than Alpine to optimize image size. Distroless (https://github.com/GoogleContainerTools/distroless) is a good example.
- Smaller and Safer Clojure Containers: Minimizing the Software Bill of Materials
-
Long Term Ownership of an Event-Driven System
The same as our code dependencies, container updates can include security patches and bug fixes and improvements. However, they can also include breaking changes and it is crucial you test them thoroughly before putting them into production. Wherever possible, I recommend using the distroless base image which will drastically reduce both your image size, your risk vector, and therefore your maintenance version going forward.
-
Minimizing Nuxt 3 Docker Images
# Use a large Node.js base image to build the application and name it "build" FROM node:18-alpine as build WORKDIR /app # Copy the package.json and package-lock.json files into the working directory before copying the rest of the files # This will cache the dependencies and speed up subsequent builds if the dependencies don't change COPY package*.json /app # You might want to use yarn or pnpm instead RUN npm install COPY . /app RUN npm run build # Instead of using a node:18-alpine image, we are using a distroless image. These are provided by google: https://github.com/GoogleContainerTools/distroless FROM gcr.io/distroless/nodejs:18 as prod WORKDIR /app # Copy the built application from the "build" image into the "prod" image COPY --from=build /app/.output /app/.output # Since this image only contains node.js, we do not need to specify the node command and simply pass the path to the index.mjs file! CMD ["/app/.output/server/index.mjs"]
-
Build Your Own Docker with Linux Namespaces, Cgroups, and Chroot
Lots of examples without the entire OS as other comments mention, an example would be Googles distroless[0]
[0]: https://github.com/GoogleContainerTools/distroless
-
Reddit temporarily ban subreddit and user advertising rival self-hosted platform (Lemmy)
Docker doesn't do this all the time. Distroless Docker containers are relatively common. https://github.com/GoogleContainerTools/distroless
-
Why elixir over Golang
Deployment: https://github.com/GoogleContainerTools/distroless
-
Reviews
Or use distroless image as it includes one, among others. https://github.com/GoogleContainerTools/distroless/blob/main/base/README.md
What are some alternatives?
wasi-experimental-http - Experimental outbound HTTP support for WebAssembly and WASI
iron-alpine - Hardened alpine linux baseimage for Docker.
wasmer-python - 🐍🕸 WebAssembly runtime for Python
spring-boot-jib - This project is about Containerizing a Spring Boot Application With Jib
wasm-to-oci - Use OCI registries to distribute Wasm modules
jib - 🏗 Build container images for your Java applications.
wizer - The WebAssembly Pre-Initializer
podman - Podman: A tool for managing OCI containers and pods.
dioxus - Fullstack GUI library for web, desktop, mobile, and more.
dockerfiles - Various Dockerfiles I use on the desktop and on servers.
wasi-vfs - A virtual filesystem layer for WASI.
docker-alpine - Official Alpine Linux Docker image. Win at minimalism!