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
Describe the bug
raspi5 with OS Bookworm
The container is created with portainer, starts successfully and is listed as "running".
But then this (Error description):
File 1.22.0/data/unbound.sh
Lines 394 to 401 are not executed.
The Container log shows:
exec /unbound.sh: exec format error
To Reproduce
Steps to reproduce the behavior:
Docker portainer:
Entries in portainer:
my-unbound
mvance/unbound:1.22.0
53:53 tcp
53:53 udp
Volumes
Container: /opt/unbound/etc/unbound as Volume
Volume: unbound_data - local
Network
Network: macvlan
IPV4 Subnet - 192.168.178.0 /24
IPV4 Gateway - 192.168.178.1
IPV4 IP Range - 192.168.178.16/28
IPV4 Excluded IPs
Hostname: unbound
IPv4 Address: 192.168.178.18
Restart policy: Always
Expected behavior
A clear and concise description of what you expected to happen.
Error messages
The container starts and is listed as "running". In the container log, however, the following is repeated continuously (in a continuous loop):
exec /unbound.sh: exec format error
Additional context
The directories "dev" and "var" are not created. The group and user "_unbound" are not created, unfortunately I have no idea whether they are created. The last line with the execution command gives the error message that "unbound" is a directory and therefore cannot be executed. So do not get to the end of the line where the "unbound.conf" is located.
Describe the bug
raspi5 with OS Bookworm
The container is created with portainer, starts successfully and is listed as "running".
But then this (Error description):
File 1.22.0/data/unbound.sh
Lines 394 to 401 are not executed.
The Container log shows:
exec /unbound.sh: exec format error
To Reproduce
Steps to reproduce the behavior:
Entries in portainer:
my-unbound
mvance/unbound:1.22.0
53:53 tcp
53:53 udp
Volumes
Container: /opt/unbound/etc/unbound as Volume
Volume: unbound_data - local
Network
Network: macvlan
IPV4 Subnet - 192.168.178.0 /24
IPV4 Gateway - 192.168.178.1
IPV4 IP Range - 192.168.178.16/28
IPV4 Excluded IPs
Hostname: unbound
IPv4 Address: 192.168.178.18
Restart policy: Always
root@raspi5:/opt/unbound/etc/unbound# ls -la
insgesamt 36
drwxr-xr-x 2 root root 4096 28. Okt 14:30 .
drwxr-xr-x 3 root root 4096 21. Sep 13:05 ..
-rw-r--r-- 1 root root 135 21. Sep 13:30 a-records.conf
-rw-r--r-- 1 root root 95 21. Sep 13:32 srv-records.conf
-rw-r--r-- 1 root root 16814 22. Okt 17:38 unbound.conf
-rw-r--r-- 1 root root 0 21. Sep 13:26 unbound.log
root@raspi5:/var/lib/docker/volumes# ls -l
insgesamt 104
brw------- 1 root root 259, 2 28. Okt 11:48 backingFsBlockDev
-rw------- 1 root root 131072 28. Okt 12:05 metadata.db
drwx-----x 3 root root 4096 16. Sep 18:15 portainer_data
drwx-----x 2 root root 4096 28. Okt 11:02 unbound_data >>>>
root@raspi5:/var/lib/docker/volumes/unbound_data# ls -la
insgesamt 12
drwx-----x 3 root root 4096 28. Okt 12:11 .
drwx-----x 4 root root 4096 28. Okt 11:48 ..
drwxr-xr-x 2 root root 4096 28. Okt 12:12 _data
Expected behavior
A clear and concise description of what you expected to happen.
Error messages
The container starts and is listed as "running". In the container log, however, the following is repeated continuously (in a continuous loop):
exec /unbound.sh: exec format error
Additional context
The directories "dev" and "var" are not created. The group and user "_unbound" are not created, unfortunately I have no idea whether they are created. The last line with the execution command gives the error message that "unbound" is a directory and therefore cannot be executed. So do not get to the end of the line where the "unbound.conf" is located.
Thank you for your attention!
The text was updated successfully, but these errors were encountered: