This worked for me. And I agree, this could have easily been avoided. The HA devs might feel otherwise, but when you allow users to do custom installations, you should not gatekeep things.
1 Like
I’m still not great with Docker stuff - but when I started, I used docker-compose, and so now I try to keep everything in docker-compose. So, anyone able/willing to translate this for what I would need to do to run Portainer with a different image and container name? My current docker-compose.yaml is below:
version: '3'
services:
portainer:
image: portainer/portainer-ce:latest
container_name: portainer
restart: unless-stopped
security_opt:
- no-new-privileges:true
volumes:
- /etc/localtime:/etc/localtime:ro
- /var/run/docker.sock:/var/run/docker.sock:ro
- ./portainer-data:/data
ports:
- 9443:9443
And in order to update portainer I run:
sudo docker-compose pull && sudo docker-compose up -d
Any update from the team on this?
I understand marking system as having unsupported software but PREVENTING UPDATES? come on? Home assistant is already hard enough to use, but to add another reason people have to google why they can’t update? That’s exactly how i found this thread and solution to my issue.
yeah, sort of… and before we’re all going to get our pitchforks - sadly, it won’t matter if we would.
OK I’m calling uncle. Going to try and rebuild years of customizations and integrations from scratch. Want to try adding it to my Hyper-V environment and pray I can get the Z-Wave USB device to pass thru. Anyway, what is the “right” platform to use going forward?
Is this the appropriate path to take to be fully supported by downloading this Hyper-V drive image?
Good luck… HyperV and USB hardware passthrough is error prone. Speaking from experience. Personally, I’d avoid HyperV at all costs. Go with WSL2 if you have access to HyperV as it will be much easier.
Yeah I would hate to install anything else physically on my Hypervisor but was also thinking of from what I heard that I can install ZWaveJS on the Windows side and it can communicate with HA thru ports I guess? Note I’m looking for go forward supported so if I setup WSL2 where does that leave me with HA compatibility?
So you aren’t supported right now? What are you running on? Why is windows the main OS?
No apparently as I’m having the same issues as everyone else in this thread my current install is not a go forward supported setup. Manual install Linux, HA, etc. Or the fact I have Portainer to manage my docker instances is not supported.
debian? You should be fine.
you can ignore unhealthy conditions to get around the portainer issue.
ha jobs options --ignore-conditions healthy
moving to hyper v wont solve any of these issues. Typically what people do to run HA and get addons is to run proxmox or something similar. Have your extra containers on another virtual machine.
I personally run on debian supervised and I don’t bother with portainer because it doesn’t help solve any issues.
What other containers are you even running that necessitate running supervised?
1 Like
Helping a friend
battling with this error also, trying to install newest 2023.3.5 update,… or make tat actually trying to get the Cloudflare tunnel installed but being blocked by the system health.
don’t have portioner installed.
can’t install a ssh tool to get to terminal
have restarted platform multiple times now.
settings/system/repair => unignore
it’s saying something was ignore in 2023.3.4
HA is running on a Pi, headless, no KB.
G
Fixed… nothing like following Microsoft fixing principles… hard restart everything…
G
Having the same Problem, I think your best bet is to just wipe it! start with a fresh install. All the fixes I’ve found did not work so it has stayed broken for mouths now.
HA is running on intel noke, headless.
Do that command every night with crontab
Haha nice workaround. I wish it wasn’t needed, but this works for now. Portainer is super handy. I wasn’t able to use my Nvidia GPU with Frigate when it was running as the HASS addon, so I had to run it on the server with docker-compose. Portainer makes it so easy to create a new stack and paste in the config. But I guess I can see how it causes a lot of problems for the devs.
For information, I solved with the portable version of windows:
then I launch it with a .BAT/.CMD that contains:
@START /min portainer.exe --data=c:\portainer
@“C:\Program Files\Google\Chrome\Application\chrome.exe” --app=http://localhost:9000/
to be adjusted according to your browser.
Dears,
I think I have the same issue. My Home Assistant Supervised running on docker on a Raspberry Pi 4 and having a Portioner stops unexpectedly, at least once per day.
Do you have an idea what would be the best solution?
2024-03-08 01:04:39.853 WARNING (MainThread) [homeassistant.components.sonos.speaker] No recent activity and cannot reach Kitchen, marking unavailable
2024-03-08 01:04:39.856 WARNING (MainThread) [homeassistant.components.sonos.speaker] No recent activity and cannot reach Living Room, marking unavailable
s6-rc: info: service legacy-services: stopping
2024-03-08 01:25:11.039 ERROR (Thread-4) [pychromecast.socket_client] [Dining room display(192.168.1.22):8009] Failed to connect. No retries.
2024-03-08 01:25:11.464 WARNING (MainThread) [homeassistant.core] Task <Task pending name='Task-172742' coro=<EntityPlatform._update_entity_states() running at /usr/src/homeassistant/homeassistant/helpers/entity_platform.py:1002> wait_for=<Future pending cb=[BaseSelectorEventLoop._sock_write_done(28, handle=<Handle BaseS....155', 8002))>)(), Task.task_wakeup()]> cb=[set.remove()]> was still running after final writes shutdown stage; Integrations should cancel non-critical tasks when receiving the stop event to prevent delaying shutdown
2024-03-08 01:25:11.470 WARNING (MainThread) [homeassistant.core] Task <Task pending name='Task-1685' coro=<MiniServer.start_loxone() running at /config/custom_components/loxone/miniserver.py:166> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[set.remove()]> was still running after final writes shutdown stage; Integrations should cancel non-critical tasks when receiving the stop event to prevent delaying shutdown
[00:25:14] INFO: Home Assistant Core finish process exit code 0
[00:25:14] INFO: Home Assistant Core service shutdown
24-03-08 01:24:15 INFO (MainThread) [supervisor.resolution.check] System checks complete
24-03-08 01:24:15 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
24-03-08 01:24:15 ERROR (MainThread) [supervisor.resolution.evaluations.container] Found image in unhealthy image list 'portainer/portainer' on the host
24-03-08 01:24:15 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
24-03-08 01:24:15 CRITICAL (MainThread) [supervisor.jobs] The following job conditions are ignored and will make the system unstable when they occur: {<JobCondition.HEALTHY: 'healthy'>}
24-03-08 01:24:15 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state running
24-03-08 01:24:15 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
24-03-08 01:24:15 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/esphome/home-assistant-addon repository
24-03-08 01:24:15 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/hassio-addons/repository repository
24-03-08 01:24:15 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/home-assistant/addons repository
24-03-08 01:24:17 INFO (MainThread) [supervisor.store] Loading add-ons from store: 77 all - 0 new - 0 remove
24-03-08 01:24:17 INFO (MainThread) [supervisor.store] Loading add-ons from store: 77 all - 0 new - 0 remove
s6-rc: info: service legacy-services: stopping
24-03-08 01:25:03 INFO (MainThread) [supervisor.api] Stopping API on 172.30.32.2
24-03-08 01:25:03 INFO (MainThread) [supervisor.misc.scheduler] Shutting down scheduled tasks
24-03-08 01:25:03 INFO (MainThread) [supervisor.docker.monitor] Stopped docker events monitor
I am still struggling with this conflict between Portioner and Home Assistant Supervised. I tried the nightly execution of “ha jobs options --ignore-conditions healthy” but at 1h20 something is the supervised container is stopping.
Any other suggestion Thanks!
I was just too fed up with poor performance/speed and issues, so i switched from supervised on a pi 4 to a 2011 laptop through a VM. Bridging in qemu/kvm and linux was a bit annoying to set up, but now its as if it runs HAOS and has 0 issues. Bluetooth passthrough was also very easy - the internsl Bluetooth chip was connected over a usb bus.
Thanks !
I still think I can make it work 
I stopped the portioner docker and surprisingly , I am running the “ha jobs options --ignore-conditions healthy” regularly and surprisingly it still complained about portioner
ONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
a2c9bfe47704 portainer/portainer "/portainer -H unix:…" 31 hours ago Exited (2) 31 hours ago
d416a1cb70bd ghcr.io/home-assistant/raspberrypi4-64-homeassistant:2024.3.0 "/init" 11 days ago Exited (137) 17 hours ago
24-03-17 11:38:43 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
24-03-17 11:38:43 INFO (MainThread) [supervisor.host.services] Updating service information
24-03-17 11:38:43 INFO (MainThread) [supervisor.host.network] Updating local network information
24-03-17 11:38:43 ERROR (MainThread) [supervisor.resolution.evaluations.container] Found image in unhealthy image list 'portainer/portainer' on the host
24-03-17 11:38:43 WARNING (MainThread) [supervisor.resolution.evaluations.base] Found unsupported images: {'eclipse-mosquitto', 'portainer/portainer', 'teslamate/grafana', 'teslamate/teslamate', 'postgres'} (more-info: https://www.home-assistant.io/more-info/unsupported/software)
24-03-17 11:38:44 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
24-03-17 11:38:44 INFO (MainThread) [supervisor.host.manager] Host information reload completed
24-03-17 11:38:44 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
24-03-17 11:38:44 CRITICAL (MainThread) [supervisor.jobs] The following job conditions are ignored and will make the system unstable when they occur: {<JobCondition.HEALTHY: 'healthy'>}
24-03-17 11:38:44 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state running
24-03-17 11:38:44 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
24-03-17 11:42:06 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
24-03-17 11:42:07 ERROR (MainThread) [supervisor.resolution.evaluations.container] Found image in unhealthy image list 'portainer/portainer' on the host
24-03-17 11:42:07 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
24-03-17 11:42:36 CRITICAL (MainThread) [supervisor.jobs] The following job conditions are ignored and will make the system unstable when they occur: {<JobCondition.HEALTHY: 'healthy'>}
24-03-17 11:42:37 WARNING (MainThread) [supervisor.jobs] 'HomeAssistantCore.update' blocked from execution, supervisor needs to be updated first
24-03-17 11:42:42 INFO (MainThread) [supervisor.supervisor] Fetching AppArmor profile https://version.home-assistant.io/apparmor_stable.txt
24-03-17 11:42:42 INFO (MainThread) [supervisor.host.apparmor] Adding/updating AppArmor profile: hassio-supervisor
24-03-17 11:42:43 INFO (MainThread) [supervisor.supervisor] Update Supervisor to version 2024.03.0
24-03-17 11:42:43 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/aarch64-hassio-supervisor with tag 2024.03.0.
24-03-17 11:43:14 INFO (MainThread) [supervisor.misc.scheduler] Shutting down scheduled tasks
24-03-17 11:43:14 INFO (MainThread) [supervisor.docker.monitor] Stopped docker events monitor
24-03-17 11:43:14 INFO (MainThread) [supervisor.api] Stopping API on 172.30.32.2
24-03-17 11:43:14 INFO (MainThread) [supervisor.hardware.monitor] Stopped Supervisor hardware monitor
24-03-17 11:43:14 INFO (MainThread) [supervisor.dbus.manager] Closed conection to system D-Bus.
24-03-17 11:43:14 WARNING (MainThread) [supervisor.homeassistant.websocket] Connection is closed
24-03-17 11:43:14 INFO (MainThread) [supervisor.core] Supervisor is down - 0
24-03-17 11:43:14 INFO (MainThread) [__main__] Closing Supervisor