Community Developer
  • Posts

  • Joined

  • Last visited


  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

balloob's Achievements


Newbie (1/14)



  1. You can ignore that error. It has been fixed in the next release.
  2. No worries! It's my fault for trying to adopt the latest and greatest before it is out. Hope it's all okay now. I wish the beta tag would allow us to specify Docker tags (like these) so that we could offer channels a la chrome. "Release channel", "Nightly channel" etc.
  3. Alrighty, I've added "version='2' and uncommented the config.
  4. I decided to go the other route as I'm still running unRaid 6.1.9.
  5. I've commented out the config field:
  6. Alright my bad. I wanted to update them because I had to update the repo and thought I would add some missing tags by looking at gfjardim's repo. Looks like I missed some things. Fixing it now.
  7. Sorry if this is not the right thread. I am updating my Unraid templates to point the Home Assistant templates to a new repo (migrated from balloob/home-assistant to homeassistant/home-assistant). As part of the process I am cleaning up how Docker generates my images and I want to migrate from 2 repositories (home-assistant, home-assistant-dev) to 1 repository with two tags (latest, dev). However, I can't seem to find a way to specify a tag in a template. Is this possible?
  8. Make sure you not just start/stop but actually update this docker. The image is setup to track the master branch of Home Assistant and is automatically build upon every release.
  9. Please refer to Home Assistant for help with any components: (also, the Tomato component has only been tested with an old version of Tomato, so might not work with newer versions)
  10. Never saw that error before. It seems to be an issue with Unraid / your internet connection / the Docker registry.
  11. Did you map volume /config to a folder on your host? A config should be created there.
  12. If I run from bash chmod +x on the config directories it will work. But the permissions get reverted after I restart container. # From /config chmod +x . log data conf.d certs ca_certificates/
  13. If I run a bash shell inside the container and run 'mosquitto -c /config/mosquitto.conf' I get the following: root@0058acdb3406:/config# mosquitto -c mosquitto.conf 1442777398: Error: Unable to open log file /config/log/mosquitto.log for writing. 1442777398: mosquitto version 1.4.3 (build date Wed, 19 Aug 2015 12:10:03 +0100) starting 1442777398: Config loaded from mosquitto.conf. 1442777398: Error: Unable to open pwfile "/config/passwords.mqtt". 1442777398: Error opening password file "/config/passwords.mqtt".