AyslanAlves

It is in version: 6.12.4 Now docker is working, but still with some logs which I find strange, as it wasn't happening before. I'm sending the logs and diagnostics. unraid-syslog-20231028-1722.zip unraid-diagnostics-20231028-1421.zip

Gentlemen, the containers don't want to start. The error message appears: Server error I've stopped ALL of them and tried to start 1 by 1, but it won't work. Can anyone help me? GRATEFUL! Oct 26 18:37:44 Unraid nmbd[2607]: nmbd version 4.17.3 started. Oct 26 18:37:44 Unraid nmbd[2607]: Copyright Andrew Tridgell and the Samba Team 1992-2022 Oct 26 18:37:44 Unraid root: /usr/sbin/wsdd2 -d Oct 26 18:37:44 Unraid root: /usr/sbin/winbindd -D Oct 26 18:37:44 Unraid wsdd2[2621]: starting. Oct 26 18:37:44 Unraid winbindd[2622]: [2023/10/26 18:37:44.453674, 0] ../../source3/winbindd/winbindd.c:1440(main) Oct 26 18:37:44 Unraid winbindd[2622]: winbindd version 4.17.3 started. Oct 26 18:37:44 Unraid winbindd[2622]: Copyright Andrew Tridgell and the Samba Team 1992-2022 Oct 26 18:37:44 Unraid winbindd[2624]: [2023/10/26 18:37:44.458304, 0] ../../source3/winbindd/winbindd_cache.c:3116(initialize_winbindd_cache) Oct 26 18:37:44 Unraid winbindd[2624]: initialize_winbindd_cache: clearing cache and re-creating with version number 2 Oct 26 18:37:44 Unraid emhttpd: shcmd (47): /etc/rc.d/rc.avahidaemon restart Oct 26 18:37:44 Unraid root: Stopping Avahi mDNS/DNS-SD Daemon: stopped Oct 26 18:37:44 Unraid avahi-daemon[2363]: Got SIGTERM, quitting. Oct 26 18:37:44 Unraid avahi-dnsconfd[2374]: read(): EOF Oct 26 18:37:44 Unraid avahi-daemon[2363]: Leaving mDNS multicast group on interface br0.IPv4 with address 10.0.0.100. Oct 26 18:37:44 Unraid avahi-daemon[2363]: Leaving mDNS multicast group on interface lo.IPv6 with address ::1. Oct 26 18:37:44 Unraid avahi-daemon[2363]: Leaving mDNS multicast group on interface lo.IPv4 with address 127.0.0.1. Oct 26 18:37:44 Unraid avahi-daemon[2363]: avahi-daemon 0.8 exiting. Oct 26 18:37:44 Unraid root: Starting Avahi mDNS/DNS-SD Daemon: /usr/sbin/avahi-daemon -D Oct 26 18:37:44 Unraid avahi-daemon[2641]: Found user 'avahi' (UID 61) and group 'avahi' (GID 214). Oct 26 18:37:44 Unraid avahi-daemon[2641]: Successfully dropped root privileges. Oct 26 18:37:44 Unraid avahi-daemon[2641]: avahi-daemon 0.8 starting up. Oct 26 18:37:44 Unraid avahi-daemon[2641]: Successfully called chroot(). Oct 26 18:37:44 Unraid avahi-daemon[2641]: Successfully dropped remaining capabilities. Oct 26 18:37:44 Unraid avahi-daemon[2641]: Loading service file /services/sftp-ssh.service. Oct 26 18:37:44 Unraid avahi-daemon[2641]: Loading service file /services/smb.service. Oct 26 18:37:44 Unraid avahi-daemon[2641]: Loading service file /services/ssh.service. Oct 26 18:37:44 Unraid avahi-daemon[2641]: Joining mDNS multicast group on interface br0.IPv4 with address 10.0.0.100. Oct 26 18:37:44 Unraid avahi-daemon[2641]: New relevant interface br0.IPv4 for mDNS. Oct 26 18:37:44 Unraid avahi-daemon[2641]: Joining mDNS multicast group on interface lo.IPv6 with address ::1. Oct 26 18:37:44 Unraid avahi-daemon[2641]: New relevant interface lo.IPv6 for mDNS. Oct 26 18:37:44 Unraid avahi-daemon[2641]: Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1. Oct 26 18:37:44 Unraid avahi-daemon[2641]: New relevant interface lo.IPv4 for mDNS. Oct 26 18:37:44 Unraid avahi-daemon[2641]: Network interface enumeration completed. Oct 26 18:37:44 Unraid avahi-daemon[2641]: Registering new address record for 10.0.0.100 on br0.IPv4. Oct 26 18:37:44 Unraid avahi-daemon[2641]: Registering new address record for ::1 on lo.*. Oct 26 18:37:44 Unraid avahi-daemon[2641]: Registering new address record for 127.0.0.1 on lo.IPv4. Oct 26 18:37:44 Unraid emhttpd: shcmd (48): /etc/rc.d/rc.avahidnsconfd restart Oct 26 18:37:44 Unraid root: Stopping Avahi mDNS/DNS-SD DNS Server Configuration Daemon: stopped Oct 26 18:37:44 Unraid root: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon: /usr/sbin/avahi-dnsconfd -D Oct 26 18:37:44 Unraid avahi-dnsconfd[2650]: Successfully connected to Avahi daemon. Oct 26 18:37:44 Unraid emhttpd: shcmd (58): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker/' /var/lib/docker 25 Oct 26 18:37:44 Unraid emhttpd: shcmd (60): /etc/rc.d/rc.docker start Oct 26 18:37:44 Unraid root: starting dockerd ... Oct 26 18:37:45 Unraid avahi-daemon[2641]: Server startup complete. Host name is Unraid.local. Local service cookie is 1186873506. Oct 26 18:37:46 Unraid avahi-daemon[2641]: Service "Unraid" (/services/ssh.service) successfully established. Oct 26 18:37:46 Unraid avahi-daemon[2641]: Service "Unraid" (/services/smb.service) successfully established. Oct 26 18:37:46 Unraid avahi-daemon[2641]: Service "Unraid" (/services/sftp-ssh.service) successfully established. Oct 26 18:38:02 Unraid kernel: Bridge firewalling registered Oct 26 18:38:02 Unraid kernel: Initializing XFRM netlink socket Oct 26 18:38:02 Unraid avahi-daemon[2641]: Joining mDNS multicast group on interface br-149b0a308a93.IPv4 with address 172.23.0.1. Oct 26 18:38:02 Unraid avahi-daemon[2641]: New relevant interface br-149b0a308a93.IPv4 for mDNS. Oct 26 18:38:02 Unraid avahi-daemon[2641]: Registering new address record for 172.23.0.1 on br-149b0a308a93.IPv4. Oct 26 18:38:02 Unraid avahi-daemon[2641]: Joining mDNS multicast group on interface br-36c7ee71aaf3.IPv4 with address 172.24.0.1. Oct 26 18:38:02 Unraid avahi-daemon[2641]: New relevant interface br-36c7ee71aaf3.IPv4 for mDNS. Oct 26 18:38:02 Unraid avahi-daemon[2641]: Registering new address record for 172.24.0.1 on br-36c7ee71aaf3.IPv4. Oct 26 18:38:02 Unraid avahi-daemon[2641]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. Oct 26 18:38:02 Unraid avahi-daemon[2641]: New relevant interface docker0.IPv4 for mDNS. Oct 26 18:38:02 Unraid avahi-daemon[2641]: Registering new address record for 172.17.0.1 on docker0.IPv4. Oct 26 18:38:02 Unraid avahi-daemon[2641]: Joining mDNS multicast group on interface br-764b2f62b550.IPv4 with address 172.20.0.1. Oct 26 18:38:02 Unraid avahi-daemon[2641]: New relevant interface br-764b2f62b550.IPv4 for mDNS. Oct 26 18:38:02 Unraid avahi-daemon[2641]: Registering new address record for 172.20.0.1 on br-764b2f62b550.IPv4. Oct 26 18:38:02 Unraid avahi-daemon[2641]: Joining mDNS multicast group on interface br-89dda74b37a7.IPv4 with address 172.22.0.1. Oct 26 18:38:02 Unraid avahi-daemon[2641]: New relevant interface br-89dda74b37a7.IPv4 for mDNS. Oct 26 18:38:02 Unraid avahi-daemon[2641]: Registering new address record for 172.22.0.1 on br-89dda74b37a7.IPv4. Oct 26 18:38:02 Unraid avahi-daemon[2641]: Joining mDNS multicast group on interface br-cb212d041ce3.IPv4 with address 172.21.0.1. Oct 26 18:38:02 Unraid avahi-daemon[2641]: New relevant interface br-cb212d041ce3.IPv4 for mDNS. Oct 26 18:38:02 Unraid avahi-daemon[2641]: Registering new address record for 172.21.0.1 on br-cb212d041ce3.IPv4. Oct 26 18:38:02 Unraid avahi-daemon[2641]: Joining mDNS multicast group on interface br-ff6410fa84b0.IPv4 with address 172.19.0.1. Oct 26 18:38:02 Unraid avahi-daemon[2641]: New relevant interface br-ff6410fa84b0.IPv4 for mDNS. Oct 26 18:38:02 Unraid avahi-daemon[2641]: Registering new address record for 172.19.0.1 on br-ff6410fa84b0.IPv4. Oct 26 18:38:04 Unraid webGUI: Successful login user root from 10.0.10.190 Oct 26 18:38:04 Unraid kernel: br-cb212d041ce3: port 1(veth5f79d78) entered blocking state Oct 26 18:38:04 Unraid kernel: br-cb212d041ce3: port 1(veth5f79d78) entered disabled state Oct 26 18:38:04 Unraid kernel: device veth5f79d78 entered promiscuous mode Oct 26 18:38:05 Unraid kernel: br-cb212d041ce3: port 2(veth11228a8) entered blocking state Oct 26 18:38:05 Unraid kernel: br-cb212d041ce3: port 2(veth11228a8) entered disabled state Oct 26 18:38:05 Unraid kernel: device veth11228a8 entered promiscuous mode Oct 26 18:38:05 Unraid kernel: br-ff6410fa84b0: port 1(vethaa1a64a) entered blocking state Oct 26 18:38:05 Unraid kernel: br-ff6410fa84b0: port 1(vethaa1a64a) entered disabled state Oct 26 18:38:05 Unraid kernel: device vethaa1a64a entered promiscuous mode Oct 26 18:38:05 Unraid kernel: br-ff6410fa84b0: port 1(vethaa1a64a) entered blocking state Oct 26 18:38:05 Unraid kernel: br-ff6410fa84b0: port 1(vethaa1a64a) entered forwarding state Oct 26 18:38:05 Unraid kernel: br-ff6410fa84b0: port 1(vethaa1a64a) entered disabled state Oct 26 18:38:05 Unraid kernel: br-cb212d041ce3: port 3(vethfccfd10) entered blocking state Oct 26 18:38:05 Unraid kernel: br-cb212d041ce3: port 3(vethfccfd10) entered disabled state Oct 26 18:38:05 Unraid kernel: device vethfccfd10 entered promiscuous mode Oct 26 18:38:05 Unraid kernel: br-cb212d041ce3: port 3(vethfccfd10) entered blocking state Oct 26 18:38:05 Unraid kernel: br-cb212d041ce3: port 3(vethfccfd10) entered forwarding state Oct 26 18:38:05 Unraid kernel: br-cb212d041ce3: port 3(vethfccfd10) entered disabled state Oct 26 18:38:06 Unraid kernel: br-cb212d041ce3: port 4(veth045aefe) entered blocking state Oct 26 18:38:06 Unraid kernel: br-cb212d041ce3: port 4(veth045aefe) entered disabled state Oct 26 18:38:06 Unraid kernel: device veth045aefe entered promiscuous mode Oct 26 18:38:06 Unraid kernel: br-cb212d041ce3: port 4(veth045aefe) entered blocking state Oct 26 18:38:06 Unraid kernel: br-cb212d041ce3: port 4(veth045aefe) entered forwarding state Oct 26 18:38:06 Unraid kernel: br-cb212d041ce3: port 4(veth045aefe) entered disabled state Oct 26 18:38:07 Unraid nmbd[2611]: [2023/10/26 18:38:07.369126, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Oct 26 18:38:07 Unraid nmbd[2611]: ***** Oct 26 18:38:07 Unraid nmbd[2611]: Oct 26 18:38:07 Unraid nmbd[2611]: Samba name server UNRAID is now a local master browser for workgroup WORKGROUP on subnet 10.0.0.100 Oct 26 18:38:07 Unraid nmbd[2611]: Oct 26 18:38:07 Unraid nmbd[2611]: ***** Oct 26 18:38:08 Unraid kernel: br-cb212d041ce3: port 5(veth6005952) entered blocking state Oct 26 18:38:08 Unraid kernel: br-cb212d041ce3: port 5(veth6005952) entered disabled state Oct 26 18:38:08 Unraid kernel: device veth6005952 entered promiscuous mode Oct 26 18:38:08 Unraid kernel: br-cb212d041ce3: port 5(veth6005952) entered blocking state Oct 26 18:38:08 Unraid kernel: br-cb212d041ce3: port 5(veth6005952) entered forwarding state Oct 26 18:38:08 Unraid kernel: br-cb212d041ce3: port 5(veth6005952) entered disabled state Oct 26 18:38:08 Unraid kernel: cgroup: Unknown subsys name 'elogind' Oct 26 18:38:08 Unraid kernel: br-cb212d041ce3: port 6(veth13c1a04) entered blocking state Oct 26 18:38:08 Unraid kernel: br-cb212d041ce3: port 6(veth13c1a04) entered disabled state Oct 26 18:38:08 Unraid kernel: device veth13c1a04 entered promiscuous mode Oct 26 18:38:08 Unraid kernel: br-cb212d041ce3: port 6(veth13c1a04) entered blocking state Oct 26 18:38:08 Unraid kernel: br-cb212d041ce3: port 6(veth13c1a04) entered forwarding state Oct 26 18:38:08 Unraid kernel: br-cb212d041ce3: port 6(veth13c1a04) entered disabled state Oct 26 18:38:09 Unraid kernel: cgroup: Unknown subsys name 'elogind' Oct 26 18:38:09 Unraid kernel: br-cb212d041ce3: port 7(vethb21332c) entered blocking state Oct 26 18:38:09 Unraid kernel: br-cb212d041ce3: port 7(vethb21332c) entered disabled state Oct 26 18:38:09 Unraid kernel: device vethb21332c entered promiscuous mode Oct 26 18:38:09 Unraid kernel: br-cb212d041ce3: port 7(vethb21332c) entered blocking state Oct 26 18:38:09 Unraid kernel: br-cb212d041ce3: port 7(vethb21332c) entered forwarding state Oct 26 18:38:09 Unraid kernel: br-cb212d041ce3: port 7(vethb21332c) entered disabled state Oct 26 18:38:09 Unraid kernel: cgroup: Unknown subsys name 'elogind' Oct 26 18:38:10 Unraid kernel: cgroup: Unknown subsys name 'elogind' Oct 26 18:38:10 Unraid kernel: br-cb212d041ce3: port 8(veth332317e) entered blocking state Oct 26 18:38:10 Unraid kernel: br-cb212d041ce3: port 8(veth332317e) entered disabled state Oct 26 18:38:10 Unraid kernel: device veth332317e entered promiscuous mode Oct 26 18:38:10 Unraid kernel: br-cb212d041ce3: port 8(veth332317e) entered blocking state Oct 26 18:38:10 Unraid kernel: br-cb212d041ce3: port 8(veth332317e) entered forwarding state Oct 26 18:38:10 Unraid kernel: br-cb212d041ce3: port 8(veth332317e) entered disabled state Oct 26 18:38:11 Unraid kernel: cgroup: Unknown subsys name 'elogind' Oct 26 18:38:13 Unraid kernel: cgroup: Unknown subsys name 'elogind' Oct 26 18:38:15 Unraid kernel: br-cb212d041ce3: port 1(veth5f79d78) entered disabled state Oct 26 18:38:15 Unraid kernel: device veth5f79d78 left promiscuous mode Oct 26 18:38:15 Unraid kernel: br-cb212d041ce3: port 1(veth5f79d78) entered disabled state Oct 26 18:38:15 Unraid kernel: br-ff6410fa84b0: port 1(vethaa1a64a) entered disabled state Oct 26 18:38:15 Unraid kernel: device vethaa1a64a left promiscuous mode Oct 26 18:38:15 Unraid kernel: br-ff6410fa84b0: port 1(vethaa1a64a) entered disabled state Oct 26 18:38:15 Unraid kernel: br-cb212d041ce3: port 2(veth11228a8) entered disabled state Oct 26 18:38:15 Unraid kernel: device veth11228a8 left promiscuous mode Oct 26 18:38:15 Unraid kernel: br-cb212d041ce3: port 2(veth11228a8) entered disabled state Oct 26 18:38:15 Unraid kernel: br-cb212d041ce3: port 3(vethfccfd10) entered disabled state Oct 26 18:38:15 Unraid kernel: device vethfccfd10 left promiscuous mode Oct 26 18:38:15 Unraid kernel: br-cb212d041ce3: port 3(vethfccfd10) entered disabled state Oct 26 18:38:15 Unraid kernel: br-cb212d041ce3: port 1(veth11ec870) entered blocking state Oct 26 18:38:15 Unraid kernel: br-cb212d041ce3: port 1(veth11ec870) entered disabled state Oct 26 18:38:15 Unraid kernel: device veth11ec870 entered promiscuous mode Oct 26 18:38:15 Unraid kernel: br-cb212d041ce3: port 1(veth11ec870) entered blocking state Oct 26 18:38:15 Unraid kernel: br-cb212d041ce3: port 1(veth11ec870) entered forwarding state Oct 26 18:38:15 Unraid kernel: br-cb212d041ce3: port 1(veth11ec870) entered disabled state Oct 26 18:38:16 Unraid kernel: cgroup: Unknown subsys name 'elogind' Oct 26 18:38:17 Unraid kernel: br-cb212d041ce3: port 4(veth045aefe) entered disabled state Oct 26 18:38:17 Unraid kernel: device veth045aefe left promiscuous mode Oct 26 18:38:17 Unraid kernel: br-cb212d041ce3: port 4(veth045aefe) entered disabled state Oct 26 18:38:17 Unraid kernel: cgroup: Unknown subsys name 'elogind' Oct 26 18:38:18 Unraid kernel: br-cb212d041ce3: port 5(veth6005952) entered disabled state Oct 26 18:38:18 Unraid kernel: device veth6005952 left promiscuous mode Oct 26 18:38:18 Unraid kernel: br-cb212d041ce3: port 5(veth6005952) entered disabled state Oct 26 18:38:18 Unraid kernel: br-cb212d041ce3: port 2(veth8b9b520) entered blocking state Oct 26 18:38:18 Unraid kernel: br-cb212d041ce3: port 2(veth8b9b520) entered disabled state Oct 26 18:38:18 Unraid kernel: device veth8b9b520 entered promiscuous mode Oct 26 18:38:19 Unraid kernel: cgroup: Unknown subsys name 'elogind' Oct 26 18:38:20 Unraid kernel: br-cb212d041ce3: port 6(veth13c1a04) entered disabled state Oct 26 18:38:20 Unraid kernel: device veth13c1a04 left promiscuous mode Oct 26 18:38:20 Unraid kernel: br-cb212d041ce3: port 6(veth13c1a04) entered disabled state Oct 26 18:38:20 Unraid kernel: br-cb212d041ce3: port 7(vethb21332c) entered disabled state Oct 26 18:38:20 Unraid kernel: device vethb21332c left promiscuous mode Oct 26 18:38:20 Unraid kernel: br-cb212d041ce3: port 7(vethb21332c) entered disabled state Oct 26 18:38:20 Unraid kernel: br-cb212d041ce3: port 8(veth332317e) entered disabled state Oct 26 18:38:20 Unraid kernel: device veth332317e left promiscuous mode Oct 26 18:38:20 Unraid kernel: br-cb212d041ce3: port 8(veth332317e) entered disabled state Oct 26 18:38:20 Unraid kernel: br-89dda74b37a7: port 1(vethd7da95e) entered blocking state Oct 26 18:38:20 Unraid kernel: br-89dda74b37a7: port 1(vethd7da95e) entered disabled state Oct 26 18:38:20 Unraid kernel: device vethd7da95e entered promiscuous mode Oct 26 18:38:21 Unraid kernel: cgroup: Unknown subsys name 'elogind' Oct 26 18:38:22 Unraid kernel: br-cb212d041ce3: port 2(veth8b9b520) entered disabled state Oct 26 18:38:22 Unraid kernel: device veth8b9b520 left promiscuous mode Oct 26 18:38:22 Unraid kernel: br-cb212d041ce3: port 2(veth8b9b520) entered disabled state Oct 26 18:38:23 Unraid kernel: eth0: renamed from vethab6dce8 Oct 26 18:38:23 Unraid kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth11ec870: link becomes ready Oct 26 18:38:23 Unraid kernel: br-cb212d041ce3: port 1(veth11ec870) entered blocking state Oct 26 18:38:23 Unraid kernel: br-cb212d041ce3: port 1(veth11ec870) entered forwarding state Oct 26 18:38:23 Unraid kernel: IPv6: ADDRCONF(NETDEV_CHANGE): br-cb212d041ce3: link becomes ready Oct 26 18:38:23 Unraid kernel: eth1: renamed from veth3e17e82 Oct 26 18:38:23 Unraid kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethd7da95e: link becomes ready Oct 26 18:38:23 Unraid kernel: br-89dda74b37a7: port 1(vethd7da95e) entered blocking state Oct 26 18:38:23 Unraid kernel: br-89dda74b37a7: port 1(vethd7da95e) entered forwarding state Oct 26 18:38:23 Unraid kernel: IPv6: ADDRCONF(NETDEV_CHANGE): br-89dda74b37a7: link becomes ready Oct 26 18:38:24 Unraid rc.docker: container jellyfin has an additional network that will be restored: jellyfin_default; Oct 26 18:38:24 Unraid rc.docker: container nextcloud-aio-apache has an additional network that will be restored: nextcloud-aio; Oct 26 18:38:24 Unraid rc.docker: container nextcloud-aio-notify-push has an additional network that will be restored: nextcloud-aio; Oct 26 18:38:24 Unraid rc.docker: container nextcloud-aio-nextcloud has an additional network that will be restored: nextcloud-aio; Oct 26 18:38:24 Unraid avahi-daemon[2641]: Joining mDNS multicast group on interface br-89dda74b37a7.IPv6 with address fe80::42:b4ff:fe64:bbbb. Oct 26 18:38:24 Unraid avahi-daemon[2641]: New relevant interface br-89dda74b37a7.IPv6 for mDNS. Oct 26 18:38:24 Unraid avahi-daemon[2641]: Registering new address record for fe80::42:b4ff:fe64:bbbb on br-89dda74b37a7.*. Oct 26 18:38:24 Unraid avahi-daemon[2641]: Joining mDNS multicast group on interface veth11ec870.IPv6 with address fe80::a812:27ff:feae:1a30. Oct 26 18:38:24 Unraid avahi-daemon[2641]: New relevant interface veth11ec870.IPv6 for mDNS. Oct 26 18:38:24 Unraid avahi-daemon[2641]: Registering new address record for fe80::a812:27ff:feae:1a30 on veth11ec870.*. Oct 26 18:38:24 Unraid rc.docker: container nextcloud-aio-imaginary has an additional network that will be restored: nextcloud-aio; Oct 26 18:38:24 Unraid rc.docker: container nextcloud-aio-fulltextsearch has an additional network that will be restored: nextcloud-aio; Oct 26 18:38:24 Unraid rc.docker: container nextcloud-aio-redis has an additional network that will be restored: nextcloud-aio; Oct 26 18:38:24 Unraid rc.docker: container nextcloud-aio-database has an additional network that will be restored: nextcloud-aio; Oct 26 18:38:24 Unraid rc.docker: container nextcloud-aio-talk has an additional network that will be restored: nextcloud-aio; Oct 26 18:38:24 Unraid rc.docker: container nextcloud-aio-collabora has an additional network that will be restored: nextcloud-aio; Oct 26 18:38:24 Unraid rc.docker: container nextcloud-aio-mastercontainer has an additional network that will be restored: nextcloud-aio; Oct 26 18:38:24 Unraid rc.docker: container nextcloud-aio-mastercontainer has an additional network that will be restored: nextcloud_aio_default; Oct 26 18:38:24 Unraid rc.docker: container nextcloud-aio-watchtower has an additional network that will be restored: nextcloud-aio; Oct 26 18:38:25 Unraid avahi-daemon[2641]: Joining mDNS multicast group on interface vethd7da95e.IPv6 with address fe80::1cad:a7ff:feac:6296. Oct 26 18:38:25 Unraid avahi-daemon[2641]: New relevant interface vethd7da95e.IPv6 for mDNS. Oct 26 18:38:25 Unraid avahi-daemon[2641]: Registering new address record for fe80::1cad:a7ff:feac:6296 on vethd7da95e.*. Oct 26 18:38:25 Unraid rc.docker: container qbittorrent has an additional network that will be restored: qbittorrent_default; Oct 26 18:38:25 Unraid rc.docker: container nextcloud-aio-borgbackup has an additional network that will be restored: nextcloud-aio; Oct 26 18:38:25 Unraid avahi-daemon[2641]: Joining mDNS multicast group on interface br-cb212d041ce3.IPv6 with address fe80::42:beff:fe3c:b065. Oct 26 18:38:25 Unraid avahi-daemon[2641]: New relevant interface br-cb212d041ce3.IPv6 for mDNS. Oct 26 18:38:25 Unraid avahi-daemon[2641]: Registering new address record for fe80::42:beff:fe3c:b065 on br-cb212d041ce3.*. Oct 26 18:38:25 Unraid rc.docker: container nextcloud-aio-onlyoffice has an additional network that will be restored: nextcloud-aio; Oct 26 18:38:25 Unraid rc.docker: created network br0 with subnets: 10.0.0.0/20; Oct 26 18:38:25 Unraid emhttpd: nothing to sync Oct 26 18:39:32 Unraid kernel: docker0: port 1(vethe8c2ae8) entered blocking state Oct 26 18:39:32 Unraid kernel: docker0: port 1(vethe8c2ae8) entered disabled state Oct 26 18:39:32 Unraid kernel: device vethe8c2ae8 entered promiscuous mode Oct 26 18:39:33 Unraid kernel: cgroup: Unknown subsys name 'elogind' Oct 26 18:39:33 Unraid kernel: docker0: port 1(vethe8c2ae8) entered disabled state Oct 26 18:39:33 Unraid kernel: device vethe8c2ae8 left promiscuous mode Oct 26 18:39:33 Unraid kernel: docker0: port 1(vethe8c2ae8) entered disabled state unraid-diagnostics-20231026-1842.zip

OK. The only way I managed to make it work is to install directly from the apps tab. Otherwise it was not possible.

Note that there is no template related to pihole, as it was installed via compose file, not by unraid app store. If I set network_mode: "br0" and restart unraid, the container disappears and displays the error message "Error response from daemon: network". If I don't set network_mode, it will create pihole_default and it will work, but I can't get an IP directly from the router and I'm stuck with the unraid IP. Another point is that pihole uses port 53, which is also used if the virtual machines are powered on. The central problem is to set the network_mode to get the ip directly on the router, acting as a bridge. Currently I have disabled the virtual machines and I am using it without setting the network interface, as you can see in the image. That way it works fine, but I'm stuck on the docker IP (10.0.0.100) and I can't use the virtual machines at the same time. Follows current diagnostics, and current compose file, with network_mode disabled: version: "3" # More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/ # Listas em https://firebog.net/ services: pihole: container_name: pihole image: pihole/pihole:latest # For DHCP it is recommended to remove these ports and instead add: network_mode: "host" ports: - "53:53/tcp" - "53:53/udp" - "8082:80/tcp" environment: TZ: 'America/Maceio' WEBPASSWORD: 'admin' # FTLCONF_LOCAL_IPV4: '10.0.0.2' PIHOLE_DNS_: '8.8.8.8;8.8.4.4' # Volumes store your data between container upgrades volumes: - '/mnt/user/appdata/pihole/pihole:/etc/pihole' - '/mnt/user/appdata/pihole/dnsmasq.d:/etc/dnsmasq.d' # https://github.com/pi-hole/docker-pi-hole#note-on-capabilities #cap_add: # - NET_ADMIN # Recommended but not required (DHCP needs NET_ADMIN) #network_mode: "br0" restart: always unraid0-diagnostics-20220908-2057.zip

I've already tested using the unraid manager and portainer, you know? It makes no difference, the error is practically the same, with a small variation depending on the manager. In practice it always fails to start the container. I really believe it's a bug in unraid as I tested it in a VM in VirtualBox and it works normally after restarting. There is some configuration in docker that erases the network interface and when it restarts it shows the following error in the unraid logs: Error response from daemon: network 33947c...

What plugin is needed? Docker Compose Manager? I am currently using Portainer-CE + Portainer-Agent and it has been working fine with a total of 6 compose files (Stacks). I believe it is a problem when I set the network to br0 (bridge), and after restarting the container it simply disappears. I've seen a few posts on the forum, but without a definitive solution, so I'm posting. I installed Docker Compose Manager, but nothing changed. I get the same error after restarting the server. Sep 7 21:16:03 Unraid0 rc.docker: pihole: Error response from daemon: network 33947c2bdd9f667c209d465520a46f09492af05774237a9f6b267bb18e03740d not found Sep 7 21:16:03 Unraid0 rc.docker: Error: failed to start containers: pihole

I have the same problem and so far no solution. Can anyone help? Frustrating trying to run elasticsearch with unraid. mkdir: cannot create directory '/config/logs': Permission denied mkdir: cannot create directory '/config/jvm.options.d': Permission denied chown: changing ownership of '/config/data': Operation not permitted chown: changing ownership of '/config': Operation not permitted cp: cannot create regular file '/config/elasticsearch.yml': Permission denied cp: cannot create regular file '/config/jvm.options': Permission denied cp: cannot create regular file '/config/log4j2.properties': Permission denied cp: cannot create regular file '/config/my-plugins.txt': Permission denied comm: /config/my-plugins.txt: No such file or directory comm: /config/my-plugins.txt: No such file or directory Exception in thread "main" java.nio.file.NoSuchFileException: /config/jvm.options at java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92) at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106) at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111) at java.base/sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:218) at java.base/java.nio.file.Files.newByteChannel(Files.java:375) at java.base/java.nio.file.Files.newByteChannel(Files.java:426) at java.base/java.nio.file.spi.FileSystemProvider.newInputStream(FileSystemProvider.java:420) at java.base/java.nio.file.Files.newInputStream(Files.java:160) at org.elasticsearch.tools.launchers.JvmOptionsParser.readJvmOptionsFiles(JvmOptionsParser.java:167) at org.elasticsearch.tools.launchers.JvmOptionsParser.jvmOptions(JvmOptionsParser.java:128) at org.elasticsearch.tools.launchers.JvmOptionsParser.main(JvmOptionsParser.java:95) ** Press ANY KEY to close this window **