A tool for exploring a docker image layer by layer, the contents of each layer, what changs in between each layer, and discovering ways to shrink the size of your Docker/OCI image. Additionally you can run this in your CI pipeline to ensure you're keeping wasted space to a minimum.
Welcome to Neko, a self-hosted virtual browser that runs in Docker and uses WebRTC technology. Neko is a powerful tool that allows you to run a fully-functional browser in a virtual environment, giving you the ability to access the internet securely and privately from anywhere. With Neko, you can browse the web, run applications, and perform other tasks just as you would on a regular browser, all within a secure and isolated environment. Whether you are a developer looking to test web applications, a privacy-conscious user seeking a secure browsing experience, or simply someone who wants to take advantage of the convenience and flexibility of a virtual browser, Neko is the perfect solution.
In addition to its security and privacy features, Neko offers the ability for multiple users to access it simultaneously. This makes it an ideal solution for teams or organizations that need to share access to a browser, as well as for individuals who want to use multiple devices to access the same virtual environment. With Neko, you can easily and securely share access to a browser with others, without having to worry about maintaining separate configurations or settings. Whether you need to collaborate on a project, access shared resources, or simply want to share access to a browser with friends or family, Neko makes it easy to do so.
Neko is also a great tool for hosting watch parties and interactive presentations. With its virtual browser capabilities, Neko allows you to host watch parties and presentations that are accessible from anywhere, without the need for in-person gatherings. This makes it easy to stay connected with friends and colleagues, even when you are unable to meet in person. With Neko, you can easily host a watch party or give an interactive presentation, whether it's for leisure or work. Simply invite your guests to join the virtual environment, and you can share the screen and interact with them in real-time.
A reverse-engineering tool for docker environments. Takes all network connections from your docker containers and can export them as:
- graphviz .dot files
- structurizr dsl
- json stream of elements
OS-independent, it uses different strategies to get container connections. Produces detailed connections graph with ports. Fast, scans ~400 containers in around 5 seconds. Right now only established and listen connections are listed.
Google's proof-of-concept self hosted Docker registry.
Podman is a daemonless, open source, Linux native tool designed to make it easy to find, run, build, share and deploy applications using Open Containers Initiative (OCI) Containers and Container Images. Podman provides a command line interface (CLI) familiar to anyone who has used the Docker Container Engine. Most users can simply alias Docker to Podman (alias docker=podman) without any problems. Similar to other common Container Engines (Docker, CRI-O, containerd), Podman relies on an OCI compliant Container Runtime (runc, crun, runv, etc) to interface with the operating system and create the running containers. This makes the running containers created by Podman nearly indistinguishable from those created by any other common container engine.
Containers under the control of Podman can either be run by root or by a non-privileged user. Podman manages the entire container ecosystem which includes pods, containers, container images, and container volumes using the libpod library. Podman specializes in all of the commands and functions that help you to maintain and modify OCI container images, such as pulling and tagging. It allows you to create, run, and maintain those containers and container images in a production environment.
Harbor is a self-hosted Docker registry that offers a large number of additional features that big companies probably love. Among those features are vulnerability scanning, third party authentication support, cryptographic signature and authentication, and a GUI.
When you use Docker Hub, this is what you're using.
docs/deploying.md describes how to deploy Registry as a Docker container. They definitely don't make it easy to break out of their ecosystem.
Quay is a self-hosted Docker container registry. Supports Docker registry protocol v2, Docker manifest schema v2.1 and v2.2, image discovery and squashing, third-party authentication, and more.
Go from graph data to a secure and interactive visual graph app in 15 minutes. Batteries-included self-hosting of graph data apps with Streamlit, Graphistry, RAPIDS, and more!
This open source effort puts together patterns the Graphistry team has reused across many graph projects as teams go from code-heavy Jupyter notebook experiments to deploying streamlined analyst tools. Whether building your first graph app, trying an idea, or wanting to check a reference, this project aims to simplify that process. It covers pieces like: Easy code editing and deployment, a project stucture ready for teams, built-in authentication, no need for custom JS/CSS at the start, batteries-included data + library dependencies, and fast loading & visualization of large graphs.
GPU enabled.
Seems to be Docker-only.
An anonymous and ephemeral Docker image registry. Free to use. No need to sign up or login. Open source. Names of images can be UUIDs. Maximum lifetime is 24 hours.
Github: https://github.com/replicatedhq/ttl.sh
Uses Docker's registry:2 image under the hood with some extra tooling. Bluh.
Github org for Simplenetes, a full implementation of Kubernetes with shell scripts. Does not require root.
Docker re-implemented as a 100 line shell script.
A toolkit for building containers if you don't have Docker installed. Automatically garbage collects container images. Multiple output formats. Pluggable. Does not require running as root.
Namechecked for use with faasd.
Language focused docker images, minus the operating system. Put a statically linked binary in there and fire it up. Designed with Go in mind.
A self-hosted web radio management suite, including turnkey installer tools for the full radio software stack and a modern, easy-to-use web app to manage your stations. Built to run on even the most affordable VPS. Media manager, playlist manager, live DJ enabled. All done through the browser. Customizable users' player page. Supports listener requests. Can relay to other servers. REST API.
Way Docker-heavy. Written in PHP.
Notes and scripts for setting up (yet another) Raspberry Pi computing cluster. One master, at least one slave to do the actual work. The master implements a certain amount of infrastructure for the rest of the network. Includes greyprints for 3D printing a rack for the units. Uses k3s and Docker.
A Dockerized service for running a disposable e-mail service. Can be personal or public. Requires MariaDB. Has an API. Also has a web front end. Requires binding port 25/tcp.
Funky Penguin's "Geek Cookbook" is a collection of how-to guides for establishing your own container-based self-hosting platform, using either Docker Swarm or Kubernetes.
Running such a platform enables you to run self-hosted tools such as AutoPirate (Radarr, Sonarr, NZBGet and friends), Plex, NextCloud, and includes elements such as:
Automatic SSL-secured access to all services (with LetsEncrypt)
SSO / authentication layer to protect unsecured / vulnerable services
Automated backup of configuration and data
Monitoring and metrics collection, graphing and alertingRecent updates and additions are posted on the CHANGELOG, and there's a friendly community of like-minded geeks in the Discord server.
A simple terminal UI for docker and docker-compose. Written in Go, has a full text-based UI for monitoring and exploring your containers. Tries to make it easier to work with Docker and docker-compose. Keeps everything in a single terminal window with shortcuts for common Docker commands. You can add custom commands, too. Seems to also support mousing around.