HassOS I am currently running is read only system by default. I can install any official or unofficial app from HA repos added, but I can not install exactly the same app from the Portainer’s App Templates option.
I guess it is just matter of proper configuration in the Portainer for /config in the deployed container mapped to /portainer/Files/AppData/Config in the Host. Once it fails I am getting info like this error while creating mount source path ‘/portainer/Files/AppData/Config’: mkdir /portainer: read-only file system
Add-on version: 1.5.1
You are running the latest version of this add-on.
System: Home Assistant OS 6.2 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2021.8.3
Home Assistant Supervisor: 2021.06.8
When I try to click on “primary” I get the following error:
The portainer add-on is broken, the 2.6.2 version cannot add containers anymore. The error message is: Failure starting container with non-empty request body was deprecated since API v1.22 and removed in v1.24.
It seems to be there is an update, version 2.6.3 but not sure wether that fixes the issue.
Can the author of the portainer add-on @frenck please look into this?
Thanks Douglas, I already read that thread but I read no solution, just a workaround. I have HA running in an image on my Qnap and am not going to mess around with that. As a workaround I installed the reactor container on a separate container on the Qnap but that is of course not ideal. I would prefer to be able to access reactor from within hass.
Hopefully portainer will be fixed or someone will build an add-on for Reactor
If you are looking to install other containers and programs on the same machine as Home Assistant you may want to look at a Home Assistant container install. You then run Home Assistant on whatever OS or version of Linux you want that supports Docker, and can install Portainer to manage all the containers, including Home Assistant at that point, which is how I’m running it. Here’s the install instructions for Home Asssistant container - Linux - Home Assistant
You lose the add-ons, but most of the add-ons for Home Assistant, (zwavejs2mqtt, zigbee2mqtt, node red, nginx, wireguard, mariadb, etc) are available on their own that you can install through docker and/or portainer on your own, and manage yourself.
Did anyone managed to get the edge agent working? I have been trying but couldn’t do it yet. Using Docker API as endpoint working fine.
Before you ask, yes I enabled the port 8000 for the addon.
There is some detailed information here:
and decoding the key with
anyway I think the Portainer server URL setting is the problem since by default, it is 8123. Normally this should be 9000 but since portainer is only available with ingress, it is not working. I couldn’t find a way to solve this.
Any advice?
Hi,
I am also attempting the same, it appears that docker agent wants to connect with 8000 + HTTP(s). there is conflicting info on this but this page seems to say its possible just using 8000 a --Tunnel-port flag but im not sure where this flag needs to be used maybe in the deployment of the agent HOWEVER… The Portainer Edge Agent - Portainer Documentation states ““Portainer now requires that only the 9000 and 8000 TCP ports are exposed. We used to serve the UI and the Portainer API from port 9000,””
I don’t think this is possible with the addon yet unless we can expose the UI on the home assistants host port but I think that may be disabled from what I could understand
I removed Community Portainer addon;
added GitHub - alexbelgium/hassio-addons: My homeassistant addons repo to HA;
Installed Alex’s Modified Portainer Addon;
Hop over to newly installed portainer addon’s configuration page and ensure Port 9000 / 8000 are populated to allow WebUI/Edge ports to reach outside host;
NOTE: Password for this addon is in Configuration tab under SSL options (Default pw: default)
NOTE: If you connect from HomeAssistant on port 8123 ensure that you change this port to 9000 to allow the api to resolve correctly. If accessing from HA;IP:9000 this will automatically populate correctly
Guys, I get this when I push to isntall. Any suggestions how to get Portainer from Alex working pls?
The command '/bin/bash -o pipefail -c apk add --no-cache nginx && if [ "${BUILD_ARCH}" = "aarch64" ]; then ARCH="arm64"; fi && if [ "${BUILD_ARCH}" = "armhf" ]; then ARCH="arm"; fi && if [ "${BUILD_ARCH}" = "armv7" ]; then ARCH="arm"; fi && if [ "${BUILD_ARCH}" = "amd64" ]; then ARCH="amd64"; fi && curl -L -s "https://github.com/portainer/portainer/releases/download/${BUILD_UPSTREAM}/portainer-${BUILD_UPSTREAM}-linux-${ARCH}.tar.gz" | tar zxvf - -C /opt/' returned a non-zero code: 1
