fuse-overlayfs
slirp4netns
fuse-overlayfs | slirp4netns | |
---|---|---|
3 | 8 | |
482 | 682 | |
1.9% | 2.3% | |
6.2 | 7.2 | |
about 2 months ago | 10 days ago | |
C | C | |
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
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.
fuse-overlayfs
-
BTFS (BitTorrent Filesystem)
Maybe something like this? https://github.com/containers/fuse-overlayfs
-
Migrating my HomeServer to Proxmox - Thoughs on Best Practice
install static fuse-overlayfs by following "static build" section on https://github.com/containers/fuse-overlayfs
-
Printing multiple copies gets multiplied twice
echo "Downloading fuse-overlayfs" mkdir -p /usr/local/bin curl -L https://github.com/containers/fuse-overlayfs/releases/latest/download/fuse-overlayfs-x86_64 > /usr/local/bin/fuse-overlayfs chmod +x /usr/local/bin/fuse-overlayfs
slirp4netns
-
Our User Mode WireGuard Year
History likes to repeat itself:
https://github.com/rootless-containers/slirp4netns
-
How to bypass VPN/choose which apps use it on Linux? Ideally I just want the VPN to work for one app, and not touch any other data coming in/out of the computer.
It should not actually require root anymore - see https://github.com/rootless-containers/slirp4netns
-
Contributing to Telescope: Wrapping up 0.4
USER root RUN curl -o /var/lib/apt/dazzle-marks/docker.gpg -fsSL https://download.docker.com/linux/ubuntu/gpg \ && apt-key add /var/lib/apt/dazzle-marks/docker.gpg \ && add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" \ && install-packages docker-ce docker-ce-cli containerd.io RUN curl -o /usr/bin/slirp4netns -fsSL https://github.com/rootless-containers/slirp4netns/releases/download/v1.1.12/slirp4netns-$(uname -m) \ && chmod +x /usr/bin/slirp4netns
- Hetzner now provides IPv6 only dedicated servers
-
Limit network access to published port
Podman pods are kind of their own thing, networking wise, being under slirp4netns https://github.com/rootless-containers/slirp4netns
- ordinary-containerization using PODMAN?
-
podman rootless setup - questions ex ante
i foud this slirp4netns in the meantime as well. There are a bunch of other problems. with podman. I cannot use nftables and firewalld with systemd+nftables, the mentioned port-"problem" for rootless podman, ipv6 containers and some other stuff that isn't working or very config-heavy. i found a lot of github issues that are actively discussed in the past days regarding some of the mentioned topics on this post. My conclusion is that i will still use docker and will look into this in a year or so... to early imo to really switch to podman because almost no benefits to docker for me. (i want ipv6, rootless containers all the way and full nftable support)
What are some alternatives?
winfsp - Windows File System Proxy - FUSE for Windows
podman-compose - a script to run docker-compose.yml using podman
dokany - User mode file system library for windows with FUSE Wrapper
WireGuardMeshes - A text repo to feature-track WireGuard mesh software
rar2fs - FUSE file system for reading RAR archives
rootlesskit - Linux-native "fake root" for implementing rootless containers
ifuse - A fuse filesystem to access the contents of iOS devices
wireguard-go-docker - Wireguard docker image
MooseFS - MooseFS – Open Source, Petabyte, Fault-Tolerant, Highly Performing, Scalable Network Distributed File System (Software-Defined Storage)
OpenNebula - The open source Cloud & Edge Computing Platform bringing real freedom to your Enterprise Cloud 🚀
workspace-images - Ready to use docker images for Gitpod workspaces
satellite - A Microservice Framework for Telescope