You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ends with timeout. Obviously updated the path and tried executing it directly from the folder with sudo rights.
It outputs
Step 1 from 5: Testing Docker service availability
Testing... |^C
And eventually stops here. This is with the latest DSM DSM 7.2-64570 Update 1.
Workaround is i removed the check whether Docker service is available and the remaining steps run through without issues. Also the installation worked flawless.
Might be interesting, that i use bond0 as network parent (both eth0 and eth1 are being used). Not sure if that makes a difference.
Step 1 from 5: Validating DSM, Docker, and Docker Compose versions on host
Current DSM: 7.2
Current Docker: 20.10.23
Current Docker Compose: 2.9.0
Step 2 from 5: Testing network service availability
Testing... Network service detected
Step 3 from 5: Initializing network and Pi-hole settings
Interface: bond0
Subnet: 192.168.254.0/24
Gateway: 192.168.254.1
Host IP address: 192.168.254.28
VLAN: macvlan0
Pi-hole MAC address: d0:7a:c5:93:db:f4
Pi-hole IP address: 192.168.254.27
Docker network IP range: 192.168.254.27/32
Domain name: pihole.local
Hostname: pihole
Timezone: Europe/Luxembourg
Europe/Amsterdam
Europe/Brussels
DNS1: 1.1.1.1
DNS2: 1.0.0.1
Data path: /volume1/docker/synology-pihole/data
Web password: (not set)
The text was updated successfully, but these errors were encountered:
I am having the same issue, and it seems to stem from the check for Docker that you describe. When I run things manually I can see it's trying to run this command:
synopkg status Docker
...but that is failing now with this error:
{"aspect":{"active":{"status":"stop","status_code":263,"status_description":"failed to get unit status"},"error":{"status":"non_installed","status_code":255,"status_description":"failed to locate given package"}},"description":"Status: [255], No such package","package":"Docker","status":"non_installed"}
Edit: this is in fact resolved by this PR too: #28
While trying to add this to my task scheduler
/bin/sh /path/to/your/script/syno_pihole.sh network --ip 192.168.0.250 --log /var/log/syno_pihole.log --force
ends with timeout. Obviously updated the path and tried executing it directly from the folder with sudo rights.
It outputs
Step 1 from 5: Testing Docker service availability
Testing... |^C
And eventually stops here. This is with the latest DSM DSM 7.2-64570 Update 1.
Workaround is i removed the check whether Docker service is available and the remaining steps run through without issues. Also the installation worked flawless.
Might be interesting, that i use bond0 as network parent (both eth0 and eth1 are being used). Not sure if that makes a difference.
Step 1 from 5: Validating DSM, Docker, and Docker Compose versions on host
Current DSM: 7.2
Current Docker: 20.10.23
Current Docker Compose: 2.9.0
Step 2 from 5: Testing network service availability
Testing... Network service detected
Step 3 from 5: Initializing network and Pi-hole settings
Interface: bond0
Subnet: 192.168.254.0/24
Gateway: 192.168.254.1
Host IP address: 192.168.254.28
VLAN: macvlan0
Pi-hole MAC address: d0:7a:c5:93:db:f4
Pi-hole IP address: 192.168.254.27
Docker network IP range: 192.168.254.27/32
Domain name: pihole.local
Hostname: pihole
Timezone: Europe/Luxembourg
Europe/Amsterdam
Europe/Brussels
DNS1: 1.1.1.1
DNS2: 1.0.0.1
Data path: /volume1/docker/synology-pihole/data
Web password: (not set)
The text was updated successfully, but these errors were encountered: