Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →
Storage Alternatives
Similar projects and alternatives to storage
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
Moby
The Moby Project - a collaborative project for the container ecosystem to assemble container-based systems
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
railcar
Discontinued RailCar: Rust implementation of the Open Containers Initiative oci-runtime (by drahnr)
storage reviews and mentions
-
Where are the containers located on my system?
Check here: https://github.com/containers/storage/blob/main/docs/containers-storage.conf.5.md
-
Storage Solutions & Their Use Cases
One example that keeps popping up over the years is containers and ZFS or more specifically Linux kernel namespaces and ZFS. First LXD in 2016, podman in 2020 and 2021. There is docker issues in the past as well with the ZFS storage driver or overlayfs. These issues are fixed rather quickly by ZFS (because they are very good at what they do) or by upstream, but bugs keep happening. It is something I do not want to deal with. As I expect future problems with ZFS and projects that depend on specific features of the linux kernel, I prefer using something else. In this case Stratis, LVM and XFS, or LVM and ext4.
-
How to mount network storage into podman rootless container?
I tried using NFS because I know it well, and it is easy to do using ZFS. This Red Hat blog post says NFS should work and it does not work at the same time. I decided to just try. The ZFS server has no idea about the subuids on the podman host, so I had to mess around with --uidmap and --gidmap. That worked, as long as I did not use a pod. To keep things neat and simple, I tried to put all my Nextcloud containers into one pod. However, the id-mapping features cannot map multiple container IDs to the same host IDs. So, I cannot map the www-data (70) user and the postgres (82) user to localadmin (1000) on the podman host. Next, I tried directly mounting the NFS share as a volume using the '--opt type=nfs4' option when creating the volumes. Right away, I learned that rootless containers can't mount network shares. Makes a certain kind of sense and is also documented in the man page. But I first tried using root containers, to prove out the concept. The volumes mounted without complaint, but I landed back at square one because the id-mapping is not applied anywhere now. Appears to me that, NFS is a complete dud for this kind of application.
- Overlay: Support Native Rootless Mounts
-
Podman: A Daemonless Container Engine
Docker is properly attributed to, see https://github.com/containers/storage/blob/a4cc7aa79e050c976...
I think OP wanted to say that Podman hates Docker what is not I feel when I'm interacting with the community there. People who use Podman do it because of it's additional features that Docker does not have, like starting an Container from a rootfs or mounting the currect directory in a container using "." as path. It's a lot of small things that make Podman better.
-
A note from our sponsor - InfluxDB
www.influxdata.com | 25 Apr 2024
Stats
containers/storage is an open source project licensed under Apache License 2.0 which is an OSI approved license.
The primary programming language of storage is Go.
Sponsored