# juicefs mit Homebrew, Nix, scoop installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für juicefs in AI-Agent-Workflows.

## Installation

```sh
sudo av install brew:juicefs
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install juicefs
```

  Evidenz: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#juicefs
```

  Evidenz: nixpkgs package indexes: pkgs/by-name/ju/juicefs/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

### Windows

- Scoop (92%):

```sh
scoop install main/juicefs
```

  Evidenz: Scoop official bucket manifest trees: bucket/juicefs.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

## Paketfakten

- **Paketschlüssel:** brew:juicefs
- **Paketmanager:** Homebrew
- **Paketmanager-Seite:** <https://formulae.brew.sh/formula/juicefs>
- **Version:** 1.4.0
- **Quellzusammenfassung:** Cloud-based, distributed POSIX file system built on top of Redis and S3
- **Homepage:** <https://juicefs.com>
- **Repository:** <https://github.com/juicedata/juicefs>
- **Upstream-Dokumentation:** <https://juicefs.com/docs/community>
- **Lizenz:** Apache-2.0
- **Quellarchiv:** <https://github.com/juicedata/juicefs/archive/refs/tags/v1.4.0.tar.gz>
- **Zuletzt aktualisiert:** 2026-07-06T10:07:59Z
- **Generiert:** 2026-07-08T07:18:31+00:00

## Executables

- juicefs (cli)
- juicefs (Alias)

## Build-Abhängigkeiten

- go

## Installationsverhalten

- Post-install-Hook: nicht definiert
- Bottle: verfügbar auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux

## Version und Aktualität

- Seite generiert: 2026-07-08
- Manager-Version: 1.4.0
- Manager aktualisiert: 2026-07-06
- lokale Daten: OK
- Upstream-Repository: https://github.com/juicedata/juicefs
- neueste erkannte Version: v1.4.0 (aktuell)
## Projektgeschichte und Nutzung

JuiceFS is a cloud-native distributed POSIX file system that separates file data from metadata: file data lives in object storage and metadata lives in a database or key-value engine. That split made it attractive for Kubernetes, machine-learning, big-data, and cloud migration workloads that need a familiar filesystem interface over elastic storage.

### Projektgeschichte

JuiceFS project materials describe the system as started in 2017 and designed for unstructured data management across multi-cloud, cross-cloud, and hybrid-cloud environments. Its open-source Community Edition is released under Apache-2.0, and official architecture documentation explains the object-storage plus metadata-engine design.

### Adoptionsgeschichte

The project moved from an early open-source release line in 2021 to a 1.0.0 release published on August 9, 2022. Packaging in Homebrew, Nix, and Scoop made the single `juicefs` CLI easy to install across developer laptops and automation environments.

### Wie es verwendet wird

Users format a JuiceFS volume against a metadata engine, mount it through the CLI, and back file data with S3-compatible or other object storage. In package-manager terms, it is a heavyweight CLI because the same binary is both an administration tool and the client that mounts the filesystem.

### Warum Paket-Nerds sich dafür interessieren

JuiceFS is significant because it packages a distributed storage client as a normal CLI while depending on external services for durability and metadata. It sits at the intersection of FUSE filesystems, cloud object stores, Kubernetes CSI drivers, and database-backed metadata.

### Zeitleiste

- 2017: JuiceFS project materials describe the project as having started in this year.
- 2021: Public GitHub releases show the 0.x open-source release line.
- 2022: JuiceFS 1.0.0 was published on August 9.
- 2023: v1.1 documentation introduced directory statistics and directory quota behavior.

### Related projects

- Kubernetes CSI drivers are a major deployment surface for JuiceFS.
- Redis, TiKV, MySQL, PostgreSQL, and SQLite are documented metadata-engine options.
- Amazon S3 and S3-compatible object stores are common backing stores.

### Quellen

- <https://formulae.brew.sh/formula/juicefs>
- <https://github.com/juicedata/juicefs>
- <https://juicefs.com/docs/community/architecture/>
- <https://juicefs.com/docs/community/release_notes/>
- <https://juicefs.com/en/blog/release-notes/juicefs-v1>


## Sicherheitshinweise

infrastructure mutation or orchestration signal.

- **Geiger-Risiko:** orange / mittel
- infrastructure mutation or orchestration signal

## Details aus der Quelldatenbank

- **Source Database:** Homebrew formula API
- **Tap:** homebrew/core
- **Full Name:** juicefs
- **Version Scheme:** 0
- **Revision:** 0
- **Head Version:** HEAD
- **Bottle Stable Root URL:** <https://ghcr.io/v2/homebrew/core>
- **Deprecated:** no
- **Disabled:** no
- **Keg Only:** no
- **URL Keys:** head, stable

## Andere Paketmanager-Einträge

- Nix - juicefs: normalized package name match | nixpkgs package indexes: pkgs/by-name/ju/juicefs/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- Scoop - main/juicefs: normalized package name match | Scoop official bucket manifest trees: bucket/juicefs.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1


## Verwandte Links

- [Cloud CLI packages](https://www.automicvault.com/de/pkg/cloud-clis/) - Belongs to a cloud or infrastructure command family.
- [Secret-risk packages](https://www.automicvault.com/de/pkg/secret-risk-packages/) - Has protected-tool coverage, approval-gate, or non-low Geiger security signals.
- [Terminal utility packages](https://www.automicvault.com/de/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata.
- [Networking and protocol packages](https://www.automicvault.com/de/pkg/networking-protocol-tools/) - Matched network, protocol, or remote-service metadata.
- [go](https://www.automicvault.com/de/pkg/brew/go/) - Build dependency declared by Homebrew.
- [gcsfuse](https://www.automicvault.com/de/pkg/brew/gcsfuse/) - Shares av.db curated category or tags: cli, cloud-infrastructure, cloud-storage, filesystem, storage.
- [s5cmd](https://www.automicvault.com/de/pkg/brew/s5cmd/) - Shares av.db curated category or tags: cli, cloud-infrastructure, cloud-storage, filesystem, s3.
- [filen-cli](https://www.automicvault.com/de/pkg/brew/filen-cli/) - Shares av.db curated category or tags: cli, cloud-infrastructure, cloud-storage, s3, storage.
- [garage](https://www.automicvault.com/de/pkg/brew/garage/) - Shares av.db curated category or tags: cli, cloud-infrastructure, distributed-storage, s3, storage.
- [s3fs](https://www.automicvault.com/de/pkg/brew/s3fs/) - Shares av.db curated category or tags: cli, cloud-infrastructure, filesystem, s3, storage.
- [s4cmd](https://www.automicvault.com/de/pkg/brew/s4cmd/) - Shares av.db curated category or tags: cli, cloud-infrastructure, cloud-storage, s3, storage.
- [versitygw](https://www.automicvault.com/de/pkg/brew/versitygw/) - Shares av.db curated category or tags: cli, cloud-infrastructure, filesystem, s3, storage.
- [geesefs](https://www.automicvault.com/de/pkg/brew/geesefs/) - Shares av.db curated category or tags: cli, cloud-infrastructure, cloud-storage, filesystem, s3.

## Combined YAML source

View the package source record on GitHub. [combined/juicefs.yml](https://github.com/automic-vault/db/blob/main/combined/juicefs.yml)


## Quellen

- Nucleus package database
- Geiger risk classifier
- package-page enrichment
- curated package history
- package version freshness
- av.db category and tag curation
- package relationship graph
- external package-manager database matches
- cross-ecosystem install command graph