Wow, this was quick. I am quite new into this project. What do you suggest? Would you like me to open a bug to clairfy this?
Hello.
Can anyone confirm this is a bug or unwanted behavior? At least this took me a very long time to find out.
When creating a shared folder, and giving using a path where parent directories so not exist yet, OMV creates the directories for me. However, the permissions for the "additional" directories are wrong. They contain ACL with very strange settings.
Example: create a shared folder via GUI, with this path:
/this/is/a/test
(none of these folders shall exist)
the created folders have these permissions:
| this | drwx--x---+ |
| is | drwx--x---+ |
| a | drwx--x---+ |
| test | drwxrwsr-x |
Following ACL are set:
root@homeserver:/srv/dev-disk-by-uuid-b75aa0c3-07c9-4d73-ba16-5870d28ae99e# getfacl this
# file: this
# owner: root
# group: root
user::rwx
group::---
group:users:--x
mask::--x
other::---Good idea but I don't have enough local space.
How do I start a docker container manually?
And is there a way to see when it is finished to shut it down (or can it trigger it's own shutdown once the backup is finished)?
I am struggling setting up my backup via duplicati on external USB drive.
What I want to do:
What I already have:
Where I am stuck right now is, that docker cannot handle the mount as expected. I have given the path to the backup partition as bind-mount. But when duplicati container runs, and I mount the HDD on the OMV host, the HDD does not show up in the docker container. It only shows up when the HDD is mounted at the time the container starts.
I would also prefer to mount the partition in duplicati (you can run a custom script before backup which should be able to do the mount), but from within the container I cannot execute commands on the host.
What would you do in this case? Can I mount the HDD directly in the Duplicati container?
or would it be better to run a script that first mounts the HDD and then starts the container (but then, how can it detect that the backups are finished and the HDD can be unmounted?)
I also tried to hand over the whole USB drive to docker container. Strangely it shows up there but cannot be mounted
compose file:
devices:
- /dev/disk/by-uuid/2E6F-3DEF:/dev/disk/by-uuid/2E6F-3DEF
shell inside docker container:
root@9a6672ac25b3:/srv# mount /dev/disk/by-uuid/2E6F-3DEF /backups
mount: /backups: permission denied.
dmesg(1) may have more information after failed mount system call.Hi.
My setup for a simple home server: Box is a Low-Power mini-PC with only 1 internal m.2 SSD disk (2TB). 8GB RAM, non-ECC (but not everything can be used by OMV). No UPS.
Host is running proxmox with OMV as a VM. The storage drive for OMV is a virtual drive (~1.5TB needed).
I know it is recommended to pass through a whole disk to OMV, but in this case it is not possible because the host only has one m.2 socket (no SATA), and I don't like using USB for such stuff.
Raid is no issue, because a backup concept is there which is sufficient for me.
Which file system would you recommend for the storage? Are there differences or some big no-gos when it is virtualized?
I would prefer a file system with additional checksums, especially because of the additional virtualisation - so probably ZFS or BTRFS. Both seem to work for this use case. Yeah, if a checksum is wrong I would have to fetch it from backup, I suppose - but detecting failures is the first step and better than nothing.
(and I am aware that I would have to do the SMART monitoring on the host. This is a bummer, but I can live with it.)
Greetings,
exae