benflux

@jonathanmYes, they are on another controller, but I expected to see them in the devices listed saying 'managed by another controller' but they aren't there for me to attempt to adoot them.

Thank you, that did fix it 🙂

Having just installed this in host mode, I can't see any of my devices on the devices page, do I need to go and change anything on the devices on my hardware controller for them to be seen?

I don't have many things to change:

I want to access a public share via NFS from my CCTV software. It can't connect to the share and I wonder if this screenshot is saying NFS isn't enabled on the share (it is enabled globally in the settings)?

15gb backup it seems. medusa: 1.5gb plex: many more of those gigs

i've set that to weekly now, thank you.

yes that makes sense, that part seems to be working then, just the disappearing to solve.

I've noticed that my dockers all stop at approx 5am each day for maybe an hour, can't find why that's the case, I've nothing scheduled daily that I can see...perhaps that is related to why some disappear too?

I went to 50G because once it filled up and I had plenty to give it. I guess I can reduce down. Also, how do i convert from ReiserFS? I guess I should fix the original issue before doing that anyway.

where do i un-ignore these?

I replaced a drive with a bigger one (it wasn't a trigger for dockers disappearing). jackett does seem to be update frequently

Here they are...I've reinstalled the two that got deleted recently (radarr and Jackett) nas2-diagnostics-20191226-2331.zip

Every once in a while, I find that one or more of my containers vanish. I re-add them from the templates and all is good but i'd like to know how to prevent this...

hahaha. thank you.

so i need to install/configure them all again?

Attached. nas2-diagnostics-20190612-0023.zip

things i've changed of late: set network dns to be opendns parental control IPs

this is me disabling and re-enabling docker: Jun 12 09:07:41 NAS2 root: stopping dockerd ... Jun 12 09:07:42 NAS2 root: waiting for docker to die ... Jun 12 09:07:43 NAS2 avahi-daemon[4198]: Interface docker0.IPv4 no longer relevant for mDNS. Jun 12 09:07:43 NAS2 avahi-daemon[4198]: Leaving mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. Jun 12 09:07:43 NAS2 avahi-daemon[4198]: Withdrawing address record for 172.17.0.1 on docker0. Jun 12 09:07:43 NAS2 emhttpd: shcmd (264): umount /var/lib/docker Jun 12 09:07:50 NAS2 ool www[9361]: /usr/local/emhttp/plugins/dynamix/scripts/emhttpd_update Jun 12 09:07:50 NAS2 emhttpd: req (3): cmdStatus=apply&csrf_token=*************** Jun 12 09:07:50 NAS2 emhttpd: Starting services... Jun 12 09:07:50 NAS2 emhttpd: shcmd (270): /etc/rc.d/rc.samba restart Jun 12 09:07:52 NAS2 root: Starting Samba: /usr/sbin/nmbd -D Jun 12 09:07:52 NAS2 root: /usr/sbin/smbd -D Jun 12 09:07:52 NAS2 root: /usr/sbin/winbindd -D Jun 12 09:07:52 NAS2 emhttpd: shcmd (283): /usr/local/sbin/mount_image '/mnt/disk1/docker.img' /var/lib/docker 50 Jun 12 09:07:52 NAS2 kernel: BTRFS info (device loop2): disk space caching is enabled Jun 12 09:07:52 NAS2 kernel: BTRFS info (device loop2): has skinny extents Jun 12 09:07:52 NAS2 root: Resize '/var/lib/docker' of 'max' Jun 12 09:07:52 NAS2 kernel: BTRFS info (device loop2): new size for /dev/loop2 is 53687091200 Jun 12 09:07:52 NAS2 emhttpd: shcmd (285): /etc/rc.d/rc.docker start Jun 12 09:07:52 NAS2 root: starting dockerd ... Jun 12 09:07:53 NAS2 avahi-daemon[4198]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. Jun 12 09:07:53 NAS2 avahi-daemon[4198]: New relevant interface docker0.IPv4 for mDNS. Jun 12 09:07:53 NAS2 avahi-daemon[4198]: Registering new address record for 172.17.0.1 on docker0.IPv4. Jun 12 09:07:53 NAS2 kernel: IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready

After many years of running dockers, today I get this: "No Docker containers installed" - help!! (no changes were made in the days leading up to a reboot)

Has anyone had a play with Jitsi? Anyone got their docker image working? https://jitsi.org/ https://github.com/tiredofit/docker-jitsi-meet

I think you should have been getting the .py file into the docker itself (not the place where configuration.yaml exists in the appdata location) by going into the console relevant to the HA docker image, then pulling the file in there with a wget, but as far as executing it, I'm stuck there.

@DZMM did you ever get this working?

Solved it by following this guide here: https://community.home-assistant.io/t/help-smartthings-docker-unraid-installation-almost-there/10071/15 I put unique IPs on each docker and got the MAC address of the MQTT docker to put in Smartthings. SO happy.

If there is anyone that can help diagnose my inability to have Smartthings show it's devices in HASS then it will stop be tearing my hair out. I 'think' I've got HASS talking to MQTT, which seems to be talking to the Smartthings-Mqtt-Bridge, I've got the device handler, device and smartapp in Smartthings too. My issue is that Smartthings doesn't appear to be talking to the bridge because no devices show in Hass and when I view the Docker log in Unraid, there is no mention of anything incoming from Smartthings. Please can any one help?