JuiceFS false junkerderprovinz/juicefs:latest https://hub.docker.com/r/junkerderprovinz/juicefs bridge sh false https://github.com/junkerderprovinz/juicefs/blob/main/README.md https://github.com/junkerderprovinz/juicefs/issues https://github.com/juicedata/juicefs JuiceFS keeps file metadata in a database and file contents in an object store. This template runs its S3 gateway, so anything on your server that speaks S3 can talk to it. The official binary, unmodified, verified against the upstream SHA256 at build time. Why this template exists: upstream publishes no image meant to be installed as a container. Their Docker volume plugin is not a container at all and cannot be installed from a template, and their juicedata/mount image expects you to write the whole command line yourself, with the file system created by hand in a console first. Here every setting is a field below, and the file system is created on first boot. No manual CLI setup: • The file system is created the first time the container starts. On every later start it finds the existing one and leaves it alone, because formatting twice would orphan every object already stored. • Leave the Secret Key empty and one is generated for you and written to /config/.s3_root_password. The container log points you at it. • Defaults are a SQLite file in /config and a plain directory in /data, so a fresh install needs no second container and no external database. READ THIS BEFORE YOU INSTALL: JuiceFS splits files into chunks, so the Data folder is NOT browsable. You will see JuiceFS's own layout there, not your file names. Everything goes in and comes out through the S3 gateway. If you want an S3 API in front of a share you can still read normally in a file browser, install VersityGW instead. BACKUP: back up the Config and Data folders together, from the same point in time if you can. The chunks in Data are unreadable without the database in Config. A backup of only Data is not a backup. First start: watch the container log for "JUICEFS IS READY". Backup: Cloud: Network:Web Tools:Utilities https://raw.githubusercontent.com/junkerderprovinz/unraid-apps/main/juicefs/juicefs.xml https://raw.githubusercontent.com/junkerderprovinz/unraid-apps/main/juicefs/icon.png --restart=unless-stopped If this template helps you, consider buying me a coffee. https://buymeacoffee.com/junkerderprovinz Map both Config and Data, and back them up together. The chunks in Data cannot be read without the database in Config. 9000 /mnt/user/appdata/juicefs/config /mnt/user/appdata/juicefs/data /mnt/user/appdata/juicefs/cache juicefs sqlite3:///config/juicefs.db file /data/ juicefs true 99 100