distroless
telepresence
distroless | telepresence | |
---|---|---|
122 | 38 | |
17,749 | 6,359 | |
1.2% | 0.9% | |
9.4 | 9.8 | |
9 days ago | 10 days ago | |
Starlark | Go | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
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
telepresence
-
12 Factor: 13 years later
Solutions are many, and could include Docker Compose, VS Code dev containers, Telepresence, Localstack or setting up temporary AWS accounts as a development environment for serverless applications.
-
New job has no way of coding locally?
I trialled Telepresence[0] for my company 2 or 3 years ago, that does this sort of thing very slickly. It didn't quite work for us back then, I forget why, but I imagine it's come along a way since then.
[0] https://www.telepresence.io
-
Introducing a tool for running diagnostic and administrative tools locally on your machine, but with outgoing network connectivity as if they're running in your k8s cluster.
How does this compare to Telepresence?
-
Let's debug a kubernetes pod locally
seems to be very similar to https://www.telepresence.io
-
Is it ok not to be able to run application locally?
If they're web services you work on, you might try https://www.telepresence.io/ (Requires something to be installed in the cluster though, easily done).
-
Best Neovim PHP IDE option?
Depending on the context, the type of code you do, you may want to also look into the sister protocol to LSP, DAP—debug adaptor protocol. It really depends on your context whether local dev, dev against a remote server, and if the latter whether you run under GCP and thus have the “Snapshot Debugger”, or under Kubernetes with something like Ambassadar/Emissary and thus can run Telepresence, whether you do local or remote Docker and thus most IDEs don't necessarily magically work especially if the containers are competently locked down, etc.
-
LXD containers on macOS at near-native speeds
If you're on Kubernetes remotely, Telepresence [0] might be worth a look.
[0] https://www.telepresence.io
-
I wrote an OSS tool to tunnel your IDE to Kubernetes
Sounds Like Telepresence (https://github.com/telepresenceio/telepresence) which intercepts traffic to a service on the cluster and directs it to your local environment.
-
mirrord 3.0 is out - run/debug your code in the context of your k8s cluster
This seems to be very similar to Telepresence, which I just couldn't get to work for us.
-
Connecting a local container with a Kubernetes cluster
What the difference with okteto and telepresence ?
What are some alternatives?
iron-alpine - Hardened alpine linux baseimage for Docker.
devspace - DevSpace - The Fastest Developer Tool for Kubernetes ⚡ Automate your deployment workflow with DevSpace and develop software directly inside Kubernetes.
spring-boot-jib - This project is about Containerizing a Spring Boot Application With Jib
tilt - Define your dev environment as code. For microservice apps on Kubernetes.
jib - 🏗 Build container images for your Java applications.
Gravitational Teleport - The easiest, and most secure way to access and protect all of your infrastructure.
podman - Podman: A tool for managing OCI containers and pods.
skaffold - Easy and Repeatable Kubernetes Development
dockerfiles - Various Dockerfiles I use on the desktop and on servers.
teleport - A WebXR teleport for three.js
docker-alpine - Official Alpine Linux Docker image. Win at minimalism!
garden - Automation for Kubernetes development and testing. Spin up production-like environments for development, testing, and CI on demand. Use the same configuration and workflows at every step of the process. Speed up your builds and test runs via shared result caching