viddy
dive
Our great sponsors
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.
viddy
-
Safety: A comparaison between Rust, C++ and Go
Thanks for that list. I'd heard of rg and fzf but not the others.
I immediately thought: well what about Go for command line tools? Is this the viddy you speak of? https://github.com/sachaos/viddy If so, looks like it is written in Go. Looks like fzf too.
- Viddy: A modern watch command. Time machine and pager etc.
-
hwatch: A modern alternative to the watch command
I'm also a fan of Viddy which looks to be the same thing written in Go.
- viddy: π Modern watch command implemented in Go. Time machine and pager etc.
dive
-
I reduced the size of my Docker image by 40% β Dockerizing shell scripts
Dive is a great tool for debugging this. I like image reduction work just because it gives me a chance to play with Dive: https://github.com/wagoodman/dive
One easy low hanging fruit I see a LOT for ballooning image sizes is people including the kitchen sink SDK/CLI for their cloud provider (like AWS or GCP), when they really only need 1/100 of that. The full versions of both of these tools are several hundred mb each
- Dive: A tool for exploring a Docker image, layer contents and more
- FLaNK Stack Weekly for 12 September 2023
-
Top 10 CLI Tools for DevOps Teams
Whether you work with Docker regularly or even create your own Docker containers, Dive is a great tool for streamlining image sizes, potentially helping you save storage costs and speed up deployments.
-
Any Way To See The Dockerfile Used To Make An Image On Dockerhub?
If youβre happy to pull the image, then sort of yes. You can either use docker inspect or a tool like dive (https://github.com/wagoodman/dive) to see how each layer was created. This will give you an idea of the Dockerfile.
-
Issues reducing Docker image size when using Gdal and Pycurl with a multistage build?
Also, check out dive. It is an amazing tool for examining containers and find your size issues.
Did you try using dive ? It allows you to see each layer, so you can see the files that are added
-
Tips for reducing Docker image size
I like this tool: https://github.com/wagoodman/dive
-
Nix Service - Using the shipyard private crate registry with Docker
Also do I get shiny flair for https://github.com/wagoodman/dive/pull/443? Perhaps "Void shouter"?
-
Docker image size problems. This is driving me insane.
This tool is really useful for showing the size of each layer, making it obvious which layer is blowing up your image size: https://github.com/wagoodman/dive
What are some alternatives?
skopeo - Work with remote images registries - retrieving information, images, signing content
Lean and Mean Docker containers - Slim(toolkit): Don't change anything in your container image and minify it by up to 30x (and for compiled languages even more) making it secure too! (free and open source)
buildkit - concurrent, cache-efficient, and Dockerfile-agnostic builder toolkit
lnav - Log file navigator
Whaler - Program to reverse Docker images into Dockerfiles
distroless - π₯ Language focused docker images, minus the operating system.
kaniko - Build Container Images In Kubernetes
emptty - Dead simple CLI Display Manager on TTY
crun - A fast and lightweight fully featured OCI runtime and C library for running containers
jib - π Build container images for your Java applications.
gitty - Contextual information about your git projects, right on the command-line
devdash - :bento: Highly Configurable Terminal Dashboard for Developers and Creators