SaunaFS container

Base container

Build base container:

$ cd saunafs-base
$ podman build . -t saunafs-chunkserver:latest

To do:

• Provide build from source with stage container to remove building tools
• Provide a smart method to add repository if not building from source

Master

Build master container:

$ cd saunafs-master
$ podman build . -t saunafs-master:latest

Run master:

$ podman run  --net host -it --rm saunafs-master:latest -d

To do:

• Provision volume (persistence)
• Provide a configuration file from host (environment vars could be a nice and elegant solution)
• Verify that --net host is the way to go (performace wise) but should be okay
• Implement a check to preserve existent metadata !

Chunkserver

Build chunkserver container:

$ cd saunafs-chunkserver
$ podman build . -t saunafs-chunkserver:latest

To do:

• Fixed configuration example syntax error in 4.9.0 deb.
• Provide a smart way to populate sfshdd.cfg.
• Mount /mnt OR /mnt/hdd , probabily better to provide a default root /saunafs-hdd/, so you can update everything whitout restarting the container.
• Remove the argument MASTER_HOST and move to a configuration file OR env vars.
• Provide a configuration file from host

Run chunkserver:

$ podman run --net host -it --rm saunafs-chunkserver:latest 127.0.0.1 #loopback is experimental, just dev purpose

CGI monitoring

TO DO

• crate docker file

Metalogger

TO DO*

Client

How to mount client inside a container for debugging purpose, this require fuse module loaded in host kernel.

Start the container,

$ podman run -it --rm --net host --device /dev/fuse  --cap-add SYS_ADMIN saunafs-base:latest /bin/bash 

A And then mount