It's possible use all SSD space?

On the "System-> Plugins" search for and install "sharerootfs" plugin

Zitat von Pietrogramma

Thanks Soma, for you is raccomandable use the SSD boot for make the service folder of the various docker's contenitor? If it is not dangerous for system stability I would keep only my data on the two mirrored HDs and everything else on the boot ssd.
Thanks again

That's how I run my main server (although the rest of the SSD is a different partition)

sda1= /boot

sda2= root OS

sda3= docker root

DATA is on different drives (sdb && sdc )

OMV doesn't use a swap when run on USB sticks

If you did not create separate partitions on the SSD be carefull when using the root partition for data. As soon as the the root partition fills up, you get into trouble.

Care for the backup and watch free space on the disk an you can leave the docker directory on this drive. /var/lib/docker will fill up quickly.

As long as the volumes are binded with care, it will be hard to fill a 120GiB SSD.

This means only config folders or DB on the root drive

I don't have that problem since I partitioned before but the docker FS doesn't have more than 3GiB

Docker will put volumes into /var/lib/docker/volumes and images into /var/lib/docker/image.

So it depends, what you are doing with docker and if you usse docker volumes or bind mounts.

Zitat von Zoki

Docker will put volumes into /var/lib/docker/volumes and images into /var/lib/docker/image.

Not necessarily.

Before installing docker via OMV, all it takes is to change the root path to a different place (following the example I'm giviing):

And press install (the folder doesn't even exist prior to it)

So, it also lives on the same sda3 partition that I have my configs. (again 3GiB only)

/srv/dev-disk-by-label-sd_configs/@appdata

What I do care is, all DATA volumes are always set to the external drives.

/srv/dev-disk-by-label-wolf1/@data

This takes only a bit of thinking how the volumes/binds work.

Don't want to teach you anything (I know you know), just doing some explaining,

Zitat von Soma

What I do care is, all DATA volumes are always set to the external drives.

/srv/dev-disk-by-label-wolf1/@data

This takes only a bit of thinking how the volumes/binds work.

Don't want to teach you anything (I know you know), just doing some explaining,

If you know how to move docker volumes outside the /var/lib/docker directory a hint ould be very appreciated, because I do not know this.
by volumes I mean volumes created by docker volume create myVolume.

This is my problem:

If I could move individual (docker) volumes to other OS volumes, I would be more than happy. Moving the contents of the volumes to bind mounted directories is not an option for several reasons.

Zitat von Zoki

If you know how to move docker volumes outside the /var/lib/docker directory a hint ould be very appreciated, because I do not know this

Now I understand what you want.

Maybe the docker docs have something there,

Something like this:

docker volume create | Docker Documentation

It has some examples that might fit your need,

Zitat von Soma

Now I understand what you want.

Maybe the docker docs have something there,

Something like this:

docker volume create | Docker Documentation

It has some examples that might fit your need,

Alles anzeigen

If I can afford a complete partition per container, this would help, But I have to digg into the different mount options.

Do you have an Idea how to mount a directory (possibly via some loopback device)?

Bit we are getting off topic.

Zitat von Zoki

If I can afford a complete partition per container, this would help, But I have to digg into the different mount options.

Do you have an Idea how to mount a directory (possibly via some loopback device)?

Bit we are getting off topic.

Ok, see if it is good (although the mountpoint still mentions the docker root, I think it will save in the folder/volume created)

Need to make a small container using that volume and see where the data is saved.

Test scenario:

Nonexistant testvol folder on the external BTRFS drive.

Was auto-created and exists now as a docker volume.

See the spoiler

pi@tacho:~ $ ls -al /srv/dev-disk-by-label-DATA/
total 16
drwxr-xr-x 1 root root   24 Nov 22 20:27 .
drwxr-xr-x 1 root root  338 Nov 18 09:38 ..
drwxrwsrwx 1 root users   6 Nov 18 09:54 RaspberryPi4

pi@tacho:~ $ docker volume create --driver local \
> --opt type=btrfs \
> --opt device=/srv/dev-disk-by-label-DATA/testvol \
> test
test

pi@tacho:~ $ docker volume inspect test
[
    {
        "CreatedAt": "2021-12-03T21:48:25Z",
        "Driver": "local",
        "Labels": {},
        "Mountpoint": "/srv/dev-disk-by-label-sd_configs/@docker/volumes/test/_data",
        "Name": "test",
        "Options": {
            "device": "/srv/dev-disk-by-label-DATA/testvol",
            "type": "btrfs"
        },
        "Scope": "local"
    }
]

Not sure, if it helped:

$ docker volume create --driver local --opt type=ext4 --opt device=/srv/testvol test
test
$ docker volume ls
DRIVER    VOLUME NAME
local     dockergitea_db_data
local     dockergitea_gitea_data
local     dockernexus_nexus_data
local     dockersonarqube_db_data
local     dockersonarqube_sonarqube_data
local     dockersonarqube_sonarqube_extensions
local     dockeryoutrack_youtrack-conf
local     dockeryoutrack_youtrack-data
local     test
$ sudo ls data/docker/volumes
backingFsBlockDev    dockergitea_gitea_data  dockersonarqube_db_data         dockersonarqube_sonarqube_extensions  dockeryoutrack_youtrack-data  test
dockergitea_db_data  dockernexus_nexus_data  dockersonarqube_sonarqube_data  dockeryoutrack_youtrack-conf          metadata.db
$ docker run --rm -it -v test:/test debian bash
Unable to find image 'debian:latest' locally
latest: Pulling from library/debian
5e0b432e8ba9: Pull complete
Digest: sha256:45ee40a844048c2f6d0105899c1a17733530b56d481612608aab5e2e4048570b
Status: Downloaded newer image for debian:latest
docker: Error response from daemon: error while mounting volume '/var/lib/docker/volumes/test/_data': failed to mount local volume: mount /srv/testvol:/var/lib/docker/volumes/test/_data: no such file or directory.

The docker inspect looks exactly the same if you mount a smb share. The info about the share/volume is stored inside docker/volumes. Mounting takes place when running the container.

Have you ben able to run a container with the volume on your Pi?

Zitat von Zoki

Have you ben able to run a container with the volume on your Pi?

Will try it with docker hello world tomorrow, need some sleep,

Zitat von Zoki

Have you ben able to run a container with the volume on your Pi?

Just made some trials and it doesn't work,

The volume is always beeing created on the docker root, instead of the previous created external volume.

Even if it's mentioned on the yml.

Sorry but this would need more time to study than I want to waist on it.

I use the binds and it's enough for my apps.

You'll have to look for solutions but be prepared to spend some time scavaging docs,

Soma Thanks a lot, have been locking for a solution for more than a year but found nothing.

Zitat von Pietrogramma

Hi guys, this morning I created a image of my SSD 250 where I have installed the old OMV5 with Clonezilla, so if I do something wrong - and I am sure I will - I can always go back to my old system.

Have you tested this?

To be sure that it works, you need to flash it to another disk (ssd/usb stick, whatever you have available) and boot from it.

It's the only way to be sure that the backup is working OK.

Zitat von Pietrogramma

And now I'm ready to install the new OMV on the SSD. How should I proceed to create separate partitions and use all the space of the SSD for the system and use the 2HD in mirro onluy for my personal files?

With only the drive for the OS attached to the PC, just follow the guide from the forum to you case:

installing_omv5_i386_32_bit_pc [omv-extras.org]