Nothing to do with this thread.
Today when Supervisor updated I see this message:
20-08-14 23:58:53 ERROR (SyncWorker_4) [supervisor.docker] Found images: 'v2tec/watchtower' which are not supported, remove these from the host!
20-08-14 23:58:53 INFO (MainThread) [__main__] Run Supervisor
20-08-14 23:58:53 INFO (MainThread) [supervisor.api] Start API on 172.30.32.2
20-08-14 23:58:53 CRITICAL (MainThread) [supervisor.core] System running in a unsupported environment!
in the system logs… Interesting because yes, I do have a watchtower image that manages NON-Home Assistant docker images/containers… it does not touch any HA container.
There is also a message on the system tab as well as the log entry.
The error message seems a bit blunt force…
2 Likes
Running additional containers outside Home Assistant isn’t supported. You can still use your system as before, it now just lets you know.
So when is the new found “official support” for the Supervised install going to actually start to be officially supported?
I couldn’t find anywhere on the main HA website with instructions for how to install it with the new “officially supported” Supervised install method. And from other conversations I’ve had with others they can’t find it either. So if it’s there it’s hidden very well.
If the updater is going to start complaining that the way people are running their Supervised installs isn’t supported then isn’t it time to get it actually officially supported?
Unless it’s there and we just can’t find it. If so, then…nevermind.
4 Likes
Why unsuported?
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] udev.sh: executing...
[14:38:49] INFO: Update udev information
[cont-init.d] udev.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
20-08-15 14:38:51 INFO (MainThread) [supervisor.bootstrap] Use the old homeassistant repository for machine extraction
20-08-15 14:38:51 INFO (MainThread) [__main__] Initialize Supervisor setup
20-08-15 14:38:52 INFO (MainThread) [supervisor.bootstrap] Initialize Supervisor Sentry
20-08-15 14:38:52 INFO (MainThread) [supervisor.bootstrap] Setup coresys for machine: qemux86-64
20-08-15 14:38:52 INFO (SyncWorker_0) [supervisor.docker.supervisor] Attach to Supervisor homeassistant/amd64-hassio-supervisor with version 234
20-08-15 14:38:52 INFO (SyncWorker_0) [supervisor.docker.supervisor] Connect Supervisor to hassio Network
20-08-15 14:38:52 INFO (SyncWorker_0) [supervisor.docker.interface] Cleanup images: ['homeassistant/amd64-hassio-supervisor:232']
20-08-15 14:38:52 ERROR (MainThread) [supervisor.docker] Docker logging driver json-file is not supported!
20-08-15 14:38:52 INFO (MainThread) [__main__] Setup Supervisor
20-08-15 14:38:52 INFO (MainThread) [supervisor.utils.gdbus] Connect to dbus: org.freedesktop.systemd1 - /org/freedesktop/systemd1
20-08-15 14:38:53 INFO (MainThread) [supervisor.utils.gdbus] Connect to dbus: org.freedesktop.hostname1 - /org/freedesktop/hostname1
20-08-15 14:38:53 WARNING (MainThread) [supervisor.dbus.rauc] Host has no rauc support. OTA updates have been disabled.
20-08-15 14:38:53 INFO (MainThread) [supervisor.utils.gdbus] Connect to dbus: org.freedesktop.NetworkManager - /org/freedesktop/NetworkManager/DnsManager
20-08-15 14:38:53 INFO (MainThread) [supervisor.host.info] Update local host information
20-08-15 14:38:53 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
20-08-15 14:38:53 INFO (MainThread) [supervisor.host.services] Update service information
20-08-15 14:38:53 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1
20-08-15 14:38:53 INFO (MainThread) [supervisor.host.network] Update local network DNS information
20-08-15 14:38:53 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/NetworkManager/DnsManager
20-08-15 14:38:53 INFO (MainThread) [supervisor.host.sound] Update PulseAudio information
Failed to load cookie file from cookie: No such file or directory
20-08-15 14:38:53 INFO (MainThread) [supervisor.host.apparmor] Load AppArmor Profiles: {'hassio-supervisor'}
20-08-15 14:38:53 INFO (MainThread) [supervisor.host.services] Reload local service hassio-apparmor.service
20-08-15 14:38:53 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.systemd1.Manager.ReloadOrRestartUnit on /org/freedesktop/systemd1
20-08-15 14:38:53 INFO (SyncWorker_0) [supervisor.docker.interface] Attach to homeassistant/amd64-hassio-dns with version 9
20-08-15 14:38:53 INFO (MainThread) [supervisor.plugins.dns] Restart CoreDNS plugin
20-08-15 14:38:53 INFO (MainThread) [supervisor.misc.forwarder] Start DNS port forwarding to 172.30.32.3
20-08-15 14:38:53 INFO (SyncWorker_0) [supervisor.docker.interface] Restart homeassistant/amd64-hassio-dns
20-08-15 14:38:58 INFO (MainThread) [supervisor.plugins.dns] Updated /etc/resolv.conf
20-08-15 14:38:58 INFO (SyncWorker_0) [supervisor.docker.interface] Attach to homeassistant/amd64-hassio-audio with version 17
20-08-15 14:38:58 INFO (SyncWorker_0) [supervisor.docker.interface] Attach to homeassistant/amd64-hassio-cli with version 25
20-08-15 14:38:58 INFO (SyncWorker_0) [supervisor.docker.interface] Attach to homeassistant/amd64-hassio-multicast with version 2
20-08-15 14:38:58 INFO (MainThread) [supervisor.plugins.multicast] Restart Multicast plugin
20-08-15 14:38:58 INFO (SyncWorker_0) [supervisor.docker.interface] Restart homeassistant/amd64-hassio-multicast
20-08-15 14:39:02 INFO (MainThread) [supervisor.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-08-15 14:39:02 INFO (SyncWorker_0) [supervisor.docker.interface] Attach to homeassistant/qemux86-64-homeassistant with version 0.114.1
20-08-15 14:39:02 INFO (MainThread) [supervisor.hassos] No Home Assistant Operating System found
20-08-15 14:39:03 INFO (MainThread) [supervisor.store.git] Load add-on /data/addons/git/a0d7b954 repository
20-08-15 14:39:03 INFO (MainThread) [supervisor.store.git] Load add-on /data/addons/git/7ad98f9c repository
20-08-15 14:39:03 INFO (MainThread) [supervisor.store.git] Load add-on /data/addons/git/cebe7a76 repository
20-08-15 14:39:03 INFO (MainThread) [supervisor.store.git] Load add-on /data/addons/core repository
20-08-15 14:39:03 INFO (MainThread) [supervisor.store] Load add-ons from store: 69 all - 69 new - 0 remove
20-08-15 14:39:03 INFO (MainThread) [supervisor.addons] Found 11 installed add-ons
20-08-15 14:39:03 INFO (SyncWorker_4) [supervisor.docker.interface] Attach to sabeechen/hassio-google-drive-backup-amd64 with version 3.12
20-08-15 14:39:03 INFO (SyncWorker_2) [supervisor.docker.interface] Attach to homeassistant/amd64-addon-mosquitto with version 5.1
20-08-15 14:39:03 INFO (SyncWorker_1) [supervisor.docker.interface] Attach to hassioaddons/node-red-amd64 with version 7.0.0
20-08-15 14:39:03 INFO (SyncWorker_6) [supervisor.docker.interface] Attach to hassioaddons/sonweb-amd64 with version 0.11.0
20-08-15 14:39:03 INFO (SyncWorker_3) [supervisor.docker.interface] Attach to homeassistant/amd64-addon-samba with version 9.2.0
20-08-15 14:39:03 INFO (SyncWorker_4) [supervisor.docker.interface] Attach to hassioaddons/adb-amd64 with version 0.6.2
20-08-15 14:39:03 INFO (SyncWorker_7) [supervisor.docker.interface] Attach to homeassistant/amd64-addon-deconz with version 6.2.3
20-08-15 14:39:03 INFO (SyncWorker_1) [supervisor.docker.interface] Attach to homeassistant/amd64-addon-configurator with version 5.0.0
20-08-15 14:39:03 INFO (SyncWorker_5) [supervisor.docker.interface] Attach to dwelch2101/zigbee2mqtt-amd64 with version 1.14.3
20-08-15 14:39:03 INFO (SyncWorker_0) [supervisor.docker.interface] Attach to hassioaddons/portainer-amd64 with version 1.2.1
20-08-15 14:39:03 INFO (SyncWorker_2) [supervisor.docker.interface] Attach to homeassistant/amd64-addon-letsencrypt with version 4.10.0
20-08-15 14:39:03 INFO (MainThread) [supervisor.snapshots] Found 4 snapshot files
20-08-15 14:39:03 INFO (MainThread) [supervisor.discovery] Load 2 messages
20-08-15 14:39:03 INFO (MainThread) [supervisor.ingress] Load 3 ingress session
20-08-15 14:39:03 INFO (MainThread) [supervisor.misc.secrets] Load Home Assistant secrets: 9
20-08-15 14:39:04 INFO (MainThread) [__main__] Run Supervisor
20-08-15 14:39:04 INFO (MainThread) [supervisor.api] Start API on 172.30.32.2
20-08-15 14:39:04 CRITICAL (MainThread) [supervisor.core] System running in a unsupported environment!
20-08-15 14:39:04 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.INITIALIZE' start 0 add-ons
20-08-15 14:39:04 INFO (MainThread) [supervisor.core] Supervisor reboot detected
20-08-15 14:39:04 INFO (MainThread) [supervisor.misc.tasks] All core tasks are scheduled
20-08-15 14:39:04 INFO (MainThread) [supervisor.misc.hwmon] Started Supervisor hardware monitor
20-08-15 14:39:04 INFO (MainThread) [supervisor.core] Supervisor is up and running
20-08-15 14:39:04 INFO (MainThread) [supervisor.host.info] Update local host information
20-08-15 14:39:04 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
20-08-15 14:39:04 INFO (MainThread) [supervisor.host.services] Update service information
20-08-15 14:39:04 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1
20-08-15 14:39:04 INFO (MainThread) [supervisor.host.network] Update local network DNS information
20-08-15 14:39:04 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/NetworkManager/DnsManager
20-08-15 14:39:04 INFO (MainThread) [supervisor.host.sound] Update PulseAudio information
Failed to load cookie file from cookie: No such file or directory
20-08-15 14:39:07 INFO (MainThread) [supervisor.homeassistant] Updated Home Assistant API token
20-08-15 14:39:07 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-08-15 14:39:07 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
20-08-15 14:39:07 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
All I can point you at just now is the ADR. I had asked a while back and been told that the official docs were being worked on, but I don’t know any more than that.
In your case, it is the docker logging deamon that has the wrong format.
Change it from Json to journald and if you are running Debian 10 the message will go away.
Getting this too here; more than a bit annoying. Feels like the “pre-commercial” days of once-open software in my past. Also noticed it’s conveniently missing from the release notes for 0.114.1.
One could argue that nothing -or everything- is supported since this is maintained by the community, plus a handful of folks who get paid -by the community…
Perhaps rather than vandalizing the supervisor screen with “unsupported” and making us feel like outlaws, a normal text line saying “unrecommended” could be placed on the info page, along with the version, etc…
I’ve been neck-deep in Linux and Unix for 20 years. I can assure you that my install on Ubuntu 20.04 LTS, is most definitely “supported”…
Edit: Reverted to 0.114.0 and will stay here until this nonsense is removed, or HA is inevitably forked.
Edit 2: see that Supervisor 234 contains the garbage, even on 0.114.0. Will have to research how to revert that.
Terry
2 Likes
Right. And another user on here just told me that they offered to work on/help work on the docs and there offer was refused.
It kind of makes some of us think that the ADR and associated announcement that officially condones Supervised install support isn’t actually supposed to be taken seriously (being as diplomatic as possible in that phrasing).
And on a related note has there been any official numbers compiled on the percent of users who use the different installation methods now that there has been plenty of time to accrue data after the functionality was included in HA?
1 Like
Incorrect. The offered documentation was incorrect (if we talk about the same person that is… cannot tell), furthermore, a PR was never created.
Secondly, we are currently in review/creating of new and improved processes for the installation itself.
Not sure how it is commercial. You can run it the way you like, for free and the source is available for you as well. It is allowed to run it the way you like. It doesn’t limit that. This is about what the project supports and tests.
That is all.
So, the Supervisor is not related to or with the Home Assistant Core version number you are referring to in this post.
That will have no effect, since well… it isn’t related to the Home Assistant Core.
You can’t. If you want to avoid this, the recommendation is to run the Home Assistant Container installation type.
Again, this is not limiting anything, it only tells you are running something that is not according to the specification set by the project. You are free to ignore it.
Ok, I’m not going to officially speak for them out of turn. Possibly it was a miscommunication.
What about the answer to the related part of that post?
I’m missing something? What part are you referring to or are seeking an answer for?
This Part…
We don’t use that data, so no idea 
I actually said “pre-commercial” as in changes a project introduces in preparation of releasing a commercial product…
Why not find a less-obscene way to display the message? Bright red, always-there text indicates something is wrong.and should be corrected immediately. A SINGLE message in the log is more than sufficient. Anyone who installs using this method and using an UNRECOMMENDED OS is well aware of the risks and doesn’t need to see that in their face every time they go to the Supervisor screen.
Terry
Unfortunately, the real world learned us, that this isn’t the case.
Then give those of who know better, the opportunity to hide it once our hand has been slapped.
Why? It is well hidden away in a specific version/settings screen. I think it is perfectly fine in the place it is. It is not pushed in anybodies face at all. I don’t see the issue with it?
1 Like
if it’s so hidden, then why show it at all? It just isn’t needed, and feels like you’re (continuously) scolding the ones that know what they’re doing.
In the eye of the beholder I suppose…