Posts by fahrer17

Quote from ryecoaaron

If you are on 5.6.3, it should remove it. Here is the code - https://github.com/openmediava…ploy/apt/default.sls#L104 THat said, it should be a one time fix.

I'm on 5.6.3.1 and it is still present, just checked it a minute ago.

Not a big issue though, I'm just mentioning it for the records.

Quote from dleidert

Well, it seems it removes the security repository from /etc/apt/sources.list.d/openmediavault-os-security.list and then re-adds it to the same file. So there is no attempt above to remove the securiry repository from /etc/apt/sources.list to fix the issue. Thus, the error is the same.

Thanks for the clarification!

Quote from cubemin

I would just go ahead and do it. My guess is the "OMV solution" will be a future update (bug fix).

I will do so once it bothers me enough

As mentioned already: I guessed how to solve this (and was confirmed by you), I was just curious wether I'm the only one and thought I added my comment, maybe this is helpful to the dev's.

Quote from cubemin

Went to edit /etc/apt/sources.list, commenting out line 10 (the security updates repo), ran the above commands again, and now it's fixed.

This is my plan B but I wanted to check first if maybe there is something like a "OMV solution".

Quote from ryecoaaron

The update should have removed the security repo from /etc/apt/sources.list and put it in /etc/apt/sources.list.d/openmediavault-os-security.list.

Does: sudo omv-salt deploy run apt fix it?

Not for me.

This what it said afterwards:

root@OMV:~# omv-salt deploy run apt
debian:
----------
ID: configure_apt_sources_list_openmediavault
Function: file.managed
Name: /etc/apt/sources.list.d/openmediavault.list
Result: True
Comment: File /etc/apt/sources.list.d/openmediavault.list is in the correct state
Started: 15:17:40.323032
Duration: 36.079 ms
Changes:
----------
ID: remove_apt_proxy
Function: file.absent
Name: /etc/apt/apt.conf.d/99openmediavault-proxy
Result: True
Comment: File /etc/apt/apt.conf.d/99openmediavault-proxy is not present
Started: 15:17:40.359267
Duration: 0.723 ms
Changes:
----------
ID: configure_apt_pref_kernel_backports
Function: file.managed
Name: /etc/apt/preferences.d/openmediavault-kernel-backports.pref
Result: True
Comment: File /etc/apt/preferences.d/openmediavault-kernel-backports.pref is in the correct state
Started: 15:17:40.360102
Duration: 8.329 ms
Changes:
----------
ID: configure_apt_sources_list_kernel_backports
Function: file.managed
Name: /etc/apt/sources.list.d/openmediavault-kernel-backports.list
Result: True
Comment: File /etc/apt/sources.list.d/openmediavault-kernel-backports.list is in the correct state
Started: 15:17:40.368577
Duration: 8.571 ms
Changes:
----------
ID: remove_apt_sources_list_debian_security
Function: file.absent
Name: /etc/apt/sources.list.d/openmediavault-debian-security.list
Result: True
Comment: File /etc/apt/sources.list.d/openmediavault-debian-security.list is not present
Started: 15:17:40.377295
Duration: 0.586 ms
Changes:
----------
ID: remove_apt_sources_list_security_0
Function: module.run
Result: True
Comment: pkg.del_repo: Repo 'deb http://security.debian.org/debian-security buster/updates main contrib non-free' has been removed from /etc/apt/sources.list.d/openmediavault-os-security.list.
Started: 15:17:40.378618
Duration: 5319.953 ms
Changes:
----------
pkg.del_repo:
Repo 'deb http://security.debian.org/debian-security buster/updates main contrib non-free' has been removed from /etc/apt/sources.list.d/openmediavault-os-security.list.
----------
ID: configure_apt_sources_list_os_security
Function: file.managed
Name: /etc/apt/sources.list.d/openmediavault-os-security.list
Result: True
Comment: File /etc/apt/sources.list.d/openmediavault-os-security.list updated
Started: 15:17:45.698977
Duration: 17.662 ms
Changes:
----------
diff:
---
+++
@@ -1 +1,2 @@
+deb http://security.debian.org/debian-security buster/updates main contrib non-free
deb-src http://security.debian.org/debian-security buster/updates main contrib non-free
----------
ID: refresh_apt_database
Function: module.run
Name: pkg.refresh_db
Result: True
Comment:
Started: 15:17:45.716799
Duration: 0.682 ms
Changes:


Summary for debian
------------
Succeeded: 8 (changed=2)
Failed:    0
------------
Total states run:     8
Total run time:   5.393 s

But when doing another apt update the error is still there.

Quote from raulfg3

works for me:

Perfect! Exactly what I was looking for! 👍

(No idea how I could miss this 🤦🏻‍♂️)

Edit: Forgot to say thank you - thank you!

Quote from ryecoaaron

Here is how the man page explains it

Yes, I know the man page, these explanations are more or less used in the minidlna.conf as well.

The problem for me is I don't understand how the root container section is meant. I tried some configurations that sounded useful for me but wasn't successful at all so I hope for a light push in the right direction

Quote from raulfg3

works for me:

What exactly does this? Could you go a little further into detail please?

When opening shared folders on my devices I'd like to see only my explicitly shared folders like "Music", "MyStuff" etc.

Is there a way I can get rid of the (for me unnecessary) automatic categories like "Camera", "Date Taken", "Recently Added" etc. (see photo; it's a DietPi but you can see what I mean)?

In the MiniDLNA settings tab is something with "Root Container". This sounds like it could be of help but I haven't found anything nor was I able to achieve some results.

Quote from donh

You will probably be OK. I looked at your profile and saw 4GB. Proxmox manages memory well. Watch the swap usage.

Actually my signature is a little deprecated - didn't fix it yet

Quote from donh

Good luck.

Thanks as well as for your input!

Quote from donh

I would say that is about right. More memory would be a good investment.

I know nothing beats RAM but more RAM

I just did a fresh installation of my system running OMV in Proxmox and for this I doubled my RAM from 4 to 8GB hoping this would be enough (just a little home server) and now I am adjusting my guest systems in Proxmox, atm I only plan to run three: OMV, a plain Debian/DietPi and for testing purposes a Home Assistant.

Ah yes, forgot about this:

So I just more think Proxmox is wrong. Strange...

I just reinstalled my OMV as a Proxmox Guest. Since the RAM usage is shown with different numbers I am now wondering what is correct: Proxmox, htop or OMV Dashboard?

My guess is that Proxmox is wrong because both htop and Dashboard show about 10%.

But how is Proxmox then calculating it's usage?

Thanks guys, you're absolutely right *facepalm*

I had to stop setting up my installation yesterday but as soon as I was in bed I remembered that my son interrupted me when I was setting up the fixed IP in my network settings and apparently I didn't do it properly.

I can't install OMV Extras. Neither terminal nor GUI work for me:

Using GUI:

Unable to correct missing packages.
E: Failed to fetch http://deb.debian.org/debian/pool/main/liba/libassuan/libassuan0_2.5.2-1_amd64.deb  Could not resolve 'deb.debian.org'
E: Failed to fetch http://deb.debian.org/debian/pool/main/g/gnupg2/gpgconf_2.2.12-1+deb10u1_amd64.deb  Could not resolve 'deb.debian.org'
E: Failed to fetch http://deb.debian.org/debian/pool/main/libk/libksba/libksba8_1.3.5-2_amd64.deb  Could not resolve 'deb.debian.org'
E: Failed to fetch http://deb.debian.org/debian/pool/main/n/npth/libnpth0_1.6-1_amd64.deb  Could not resolve 'deb.debian.org'
E: Failed to fetch http://deb.debian.org/debian/pool/main/g/gnupg2/dirmngr_2.2.12-1+deb10u1_amd64.deb  Could not resolve 'deb.debian.org'
E: Aborting install.
<<< *************************************

Using terminal:

root@omv:~# wget -O - https://github.com/OpenMediaVault-Plugin-Developers/packages/raw/master/install | bash
--2020-12-21 22:01:06--  https://github.com/OpenMediaVault-Plugin-Developers/packages/raw/master/install
Auflösen des Hostnamens github.com (github.com)… fehlgeschlagen: Der Name oder der Dienst ist nicht bekannt.
wget: Host-Adresse »github.com« kann nicht aufgelöst werden

I'd would be rather thankful if anybody had any hints how to solve this

Quote from raulfg3

your IP range is too small for your chosee IP 192.168.178.222 as Ip for your pihole , way you do not use a small Ip like 192.168.178.2, ?? so your gateway is 1 and your DNS resolver is 2

My OMV always had 192.168.178.200 so I thought 192.168.178.222 sounded like a good idea. Moreover I took it from here:

But 192.168.178.2 is a much better idea

Quote from raulfg3

for yor example use

choose ip_range: 192.168.178.220/28 <- This must works

and remeber macvlan_NET MUST not exist so if exist, please delete first, prior to create

As far as I understand it this is if I want IP 192.168.178.222, right?

macvlan_NET was created the first time I ran you docker compose. Do I have to delete it and recreate now when changing the ip_range?

Sorry if my questions sound stupid but this IP stuff really confuses me. I watched some videos and read the wiki several times but the more I read the less I seem to understand

Thank you for your help so far!

Whatever I tried, whatever tut I tested (and I tested them all ), I have no luck in getting a PiHole to work on my OMV.

Using PiHole's official Docker compose (adapted for my needs) starts but isn't be used by any client (at least that's what the dashboard says:

version: 2


# More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/
services:
pihole:
container_name: pihole
image: pihole/pihole:latest
ports:
- "55:53/tcp"
- "55:53/udp"
- "67:67/udp"
- "80:80/tcp"
- "443:443/tcp"
environment:
TZ: Europe/Berlin
WEBPASSWORD: password
# Volumes store your data between container upgrades
volumes:
- /srv/dev-disk-by-label-Daten/Config/PiHole/etc-pihole/:/etc/pihole/
- /srv/dev-disk-by-label-Daten/Config/PiHole/etc-dnsmasq.d/:/etc/dnsmasq.d/
dns:
- 127.0.0.1
- 1.1.1.1
# Recommended but not required (DHCP needs NET_ADMIN)
#   https://github.com/pi-hole/docker-pi-hole#note-on-capabilities
# cap_add:
#  - NET_ADMIN
restart: unless-stopped

When using raulfg3's HowTo PiHole quits saying "DNS resolution is currently unavailable". Googling for this tells me to add DNS 127.0.0.1 in first place (what I did to my understanding).

# Thanks to http://tonylawrence.com/posts/unix/synology/free-your-synology-ports/ for your reference post
version: 2


services:
pihole:
container_name: pihole
image: pihole/pihole:latest
hostname: pihole
#domainname: yourdomain.org               # <-- Update or leave comment if you do not have
mac_address: d0:ca:ab:cd:ef:05           # <-- Update ( must be a random MAC, because you create a virtual NIC for it)
#cap_add:
#  - NET_ADMIN
networks:
macvlan_NET:                      # <-- MACVlan Name no need to change, but do not exist previosly.
ipv4_address: 192.168.178.222       # <-- Update; must be the IP that you want to use as DNS sever ( pihole IP)
ports:
- 443/tcp
- 53/tcp
- 53/udp
- 67/udp
- 80/tcp
environment:
ServerIP: 192.168.178.222             # <-- Update (match ipv4_address)
#VIRTUAL_HOST: pihole.yourdomain.org    # <-- Update (match hostname + domainname)
WEBPASSWORD: password         # <-- Add password (if required)
DNS1: 127.0.0.1
DNS2: 1.1.1.1                     # <-- Change by your prefered DNS service like 1.1.1.1
TZ: Europe/Berlin                 # <-- You need to add in webGUI not here
# IPv6: False                     # <-- You need to add in webGUI not here
volumes:
- /srv/dev-disk-by-label-Daten/Config/PiHole/etc-pihole/:/etc/pihole/
- /srv/dev-disk-by-label-Daten/Config/PiHole/etc-dnsmasq.d/:/etc/dnsmasq.d/
restart: unless-stopped


networks:
macvlan_NET:
driver: macvlan
driver_opts:
parent: enp0s3                        # <- Update to match your NIC see your OMV WebGUI
ipam:
config:
- subnet: 192.168.178.0/24            # <-- Update
gateway: 192.168.178.1              # <-- Update
ip_range: 192.168.178.2/28          # <-- Update

Not sure what to put in ip_range though.

What do you guys use to get it running and working?

Quote from macom

Just tried on my HC2. This docker-compose file works for me

Code

version: '2'

services:
  iobroker:
    restart: always
    image: buanet/iobroker:latest
    container_name: iobroker
    hostname: iobroker
    ports:
      - "8082:8081" #had to change for 8082 as 8081 was already in use on my system
    volumes:
      - /srv/dev-disk-by-label-Data/docker/iobrokerdata:/opt/iobroker #change the path left of ":" according your system

Display More

Takes some time to start up.

Great

I know about the path in line 12 but thanks for the hint.

What are your network settings?

This somehow confuses me:

Quote from macom

Check the docker log file. If you are using portainer there is an icon to read the log files on the right side of the container name.

Sorry I didn't mention it but I did and didn't find anything meaningful (at least for me).

Just for the records here it is:

And yes, I waited like 30mins for it to start.

Anyway, don't ask me how since I changed the network parameter back and forth (it is "bridge" now but I'm pretty sure it was before) but now it's there

I had to change to browser address from 0.0.0.0:8081 to 192.168.178.49:8081.

Is this the way to copy my ioBroker container from my virtual OMV to my "real" OMV?

https://documentation.portainer.io/v2.0/images/export/

I wanted to play around with ioBroker and installed the "official" Container (https://github.com/buanet/docker-iobroker) in a Virtualbox-OMV.

After changing the volume from

    volumes:
      - iobrokerdata:/opt/iobroker

to

    volumes:
      - /path/to/appdata/config:/opt/iobroker

(to my understanding this is for storing config data)

in its docker compose and manually switching it to "bridge" mode I was able to start and run the container successfully. But when trying to log in to ioBrokers webpage using IP_OMV:8081 or clicking the link in Portainer I can't connect to it.

Are there any hints on what I am maybe doing wrong?

I just stumbled across this thread and remembered a youtube video by DB Tech I watched recently where he explains just this.

His watchtower frequency is set to to once a week because of Docker Hub's restrictions.

I'm writing this from my work pc where youtube is blocked so unfortunately I can't provide a link; just look for his OMV+Pi series installing watchtower.

What exactly is your system setup? How many drives, what to sync from and where to etc.

I had the idea of recreating it in Virtualbox, maybe my Docker setup is successful.

Sorry, I don't find a mistake in your config (well, TIMEZONE is missing the city - no idea if this is important though). Again, I think it has something to do with permissions. I had quite trouble syncing my wife's stuff with my user and her permissions.