Posts by fahrer17

I could get hold of a decent HP400G4 so I now mess around with this machine.

Therefore I deleted everything KVM related on my OMV and no need to dive deeper into this.

Thank you so far for your assistance!

Quote from ryecoaaron

Did you create more than one subfolder in the path when creating the shared folder?

Your guess is right, I structured it like this:

/srv/dev-disk-by-uuid-ed51370e-93c2-4113-953a-41e9666acb96/

├── kvm

│   ├── KVM_ISOs

│   │   └── ubuntu-24.04.1-live-server-amd64.iso

│   └── KVM_Volumes

│   ├── ubuntu-server.qcow2

│   └── ubuntu-server.qcow2.bak

└── lost+found

Edit:

Oh, the *.qcow2 were of course meant to be inside the KVM_Volumes folder - I will check this.

I just tried a fresh ubuntu server iso with no luck, still the same error:

with ls -la

drwxrws--- 2 root users 4096 29. Jan 21:20 .

drwx--x---+ 4 root root 4096 29. Jan 20:55 ..

-rw------- 1 libvirt-qemu libvirt 26847870976 29. Jan 21:16 ubuntu-server.qcow2

-rw------- 1 root users 26847870976 29. Jan 21:11 ubuntu-server.qcow2.bak

Will need further investigation I guess...

----------------------------------------------

Edit:
After chown'ing the whole directory I was able to install ubuntu.

Next thing I will try is HA.

Thanks for your reply.

But are you sure? Because in the wiki it is said

Quote

These folders are now owned by the root user and the users group and have 2775 permissions, that's enough for it to work.

The libvirt-qemu user (id=64055) must have path access to these folders, make sure of this if you choose another way to create those folders.

omv7:omv7_plugins:kvm [omv-extras.org]

I wantedt to test the KVM plugin so I played around with it following the according omv wiki and this tutorial:

Starting a VM I got this message

Searching the internet and the forum I found this post by ryecoaaron saying to chown the *.qcow2 to libvirt-qemu user

Now do I have to do it with every new machine? Is there a way to do it in GUI (I don't have a problem using the terminal but why is there no way to do it in GUI if it seems to be important?)? Why does it seem to work in the video without chown'ing?

I had to stop ty tinkering before chown'ing so I can't report more.

I don't know what went wrong the first time but I gave it another try and everything is fine now.

What I did so far:

1. I changed the image to portainer/portainer-ce:2.20.3
2. Commented out the line - /etc/localtime:/etc/localtime:ro (it is not mentioned in the official docs)
3. Changed the ports to 8000 and 9443

So my portainer problem is solved now

Quote from raulfg3

you write bad exec docker: 'ecex'

OMG - what a stupid mistake

I did some research and as far as I can tell there are some incompatibilities between Docker version 26 (and above) and Portainer:

https://www.portainer.io/blog/portainer-and-docker-26

I did some testing in a virtual OMV, unfortunately I wasn't able to change my Portainer to the newest version (2.20.3) without loosing my containers so far but I will go on and report later.

Quote from Blabla

Hi everyone,

for people on OMV 6 how did you solved? I updated to the latest portainer version but it's 2.19.5 and the github issue ask to update to the 2.20.3

I guess it doesn't matter which OMV version you are running.

I updated to OMV7 today and can't access my containers as well. Trying to fix it using solution from #3 gives the warning that I want to install an older version (which doesn't sound useful to mee).

So is there a more recent solution for fixing this?

Edit: Trying "docker exec" doesn't work either, gives the follwing error:

docker: 'ecex' is not a docker command

raulfg3's approach is a little different than mine and I'm not sure wether I could work with his (though he is the pro and I am the noob ).

What I would do:

- In the folder you use for "data" in the docker compose settings create a folder "cups" with two subfolders "service" and "config". I usually make the "data" folder a shared folder so I can easily create accessable folders like "cups" using Windows File Explorer etc.

- Copy this to your Compose - Files - Files section and adjust it to your personal settings!

version: '3.5'

services:
  airprint:
  container_name: airprint
  image: znetwork/synology-airprint:latest
  build: .
  restart: always
  network_mode: "host"
  environment:
    CUPSADMIN: admin    # change this!
    CUPSPASSWORD: admin    # change this!
  volumes:
    - "/copy/your/data/path/cups/services:/services"    # change this!
    - "copy/your/data/path/cups/config:/config"    # change this!

Remember: Change or adjust the 4 marked lines to your settings - if unsure ask again.

You're half way there, only some little tweaks are needed

I'm not sure why your paths are like /dev/sda/, using UUID is better as I know.

Can you ssh into your server and share the output of

ls -la /srv/

What are your laptop's specs (CPU, RAM, drives tec.)? How is it connected to your network (wifi? lan?)?

I've set up several containers by now and don't use cups but this doesn't sound too complicated.

After a little searching I would use this container as it is probably still maintained: https://github.com/chuckcharlie/cups-avahi-airprint

So the general way I set up my containers:

1. Set up docker including folders for config files: https://wiki.omv-extras.org/do…v6_plugins:docker_compose
2. Create a separate folder for each application - would be "data" here: https://wiki.omv-extras.org/do…s:docker_compose#settings
3. Create the container using provided docker compose files (sometimes in OMV GUI, sometimes in portainer )

I know, a very basic explanation but feel free to ask for further assistance/details.

Home Assistant including Zigbee

Homepage dashboard

Jellyfin

MeTube - YT-Downloader

Neonlink - Collecting links

Nextcloud

Paperless-ngx

Pihole

Podgrab

Snowflake-proxy

Speedtest

Syncthing

More to come:

Photoprism or something similiar

Nginx proxy

Bitwarden (maybe)

And if your looking for ideas

GitHub - awesome-selfhosted/awesome-selfhosted: A list of Free Software network services and web applications which can be hosted on your own servers

A list of Free Software network services and web applications which can be hosted on your own servers - awesome-selfhosted/awesome-selfhosted

github.com

I wouldn't mix webmin and OMV GUI either.

I successfully installed NC folowing this great guide

Thread

[How-To] Nextcloud with swag (Letsencrypt) using OMV and docker-compose

Docker Container set up by this method can be managed by Portainer or from CLI.


Pre-requisites
In order to be able to reach nextcloud from the internet you need an external IPv4 address and a hostname.
Regarding external IPv4 address check you router or ask your internet service provider.
To register a hostname you can use services like duckdns, selfhost.eu, strato.de or many others.
Make sure to use strong passwords!!!

Preparation

• Install and fully update OMV (a restart might be needed if the kernel

…

macom

Aug 10th 2019

though without a proxy so far (will come seperatly later).

Now when I check NC's settings page in admin account I came across these messages:

Since I'm an absolute NC beginner: Is this something I should worry about?

If so how do I solve these? I tried to read and understand NC documentation but it is unfortunately of no real help for me...

Any help/advice is highly appreciated.

I'm not sure about this but couldn't you look in your new path `/srv/dev-disk-by-uuid-.../docker' what folders are there created and check the old location for corresponding folders?

This is what I would do in this case.

Now what I finally did:

1. Created a new shared folder "Backup Docker"
2. Stopped all running containers
3. Changed the path in Compose/Settings/Backup to new folder from 1.
4. Restarted Docker and all containers
5. Deleted old Backup folder using ssh

So now everything is as I wanted

I'd would try to find every point in GUI you mention on your list and after applying these new settings check smb.conf using terminal.

Sorry, I can't help more atm since I don't have access to my system.

Clear explanations - thank you for this!

How do I "tell" Docker to apply changed settings? Just hit SAVE? Or RESTART or even REINSTALL it?

When changing the location of folders (Compose Files/Data/Backup) under Compose/Files from let's say

/srv/dev123

to

/srv/dev456

is it necessary to reinstall docker or is just a restart enough?

How does a change like this affect my already existing containers?

Shall I stop the containers and do I need to recreate them? Is there anything else to observe?

There is a good (German) tutorial though I didn't complete it yet:

I managed to get my Pihole running in a docker container by follwing this guide after many unsuccessful attempts with other guieds.

The next step will be adding unbound.

But I still struggle understanding macvlan...

Quote from gderf

You can still find 16GB and 32GB 2.5inch SSD drives on ebay for very little money.

I once looked for used SSDs on ebay and they were only slightly cheaper than new ones so I decided they were not worth it but that might have been bad luck.

Anyway, it is what it is now