Everything had reset for some reason, and the add-on is no longer detech existing installation.
Log says admin account doesn’t exist, but it does:
2021/08/31 16:36:55 http error: No administrator account found inside the database (err=Object not found inside the database) (code=404)
Anyone else?
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?
See this thread…problem is solved two different ways
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
There’s an open Github issue for this Deploying any container results in error "starting container with non-empty request body was deprecated since API v1.22 and removed in v1.24" · Issue #127 · hassio-addons/addon-portainer · GitHub but I believe the position of the developers of Home Assistant is you shouldn’t be installing anything outside of the official and community addons on a supervised install.
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?
What is the default password for the add-on? Is it same as hassio root?
There isn’t one. You create a user with a username and password the first time you run it
How do I recover it. I have tried every know combination I could have set. What is the default hassio login?
There isn’t one.
You can poke around the .storage files and maybe find and delete the Portainer info and then setup a new login
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
This fork looks like it has the webui added back - testing it now https://github.com/alexbelgium/hassio-addons
Please, let me know if you got it working.
I have got it working…
For Clarity and to all whom may require the info…
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)
Start addon;
Then follow edge-agent setup guide - https://downloads.portainer.io/edge_agent_guide.pdf
(New interface instructions: Add a new endpoint - Portainer Documentation)
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
Enjoy!
Glad I took notes… Struggling with the new interface now 
Im sure it works still but to assist anyone else in the same boat this link is more updated then the former… 
Add a new endpoint - Portainer Documentation
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
Hi, pushed a v2.9.3-4 that should solve your issue. Could you please test ? Thanks
hi
Why is the official portainer discontinued?.
Read all about it below…
The developers added this note in the Readme documentation:
This add-on is no longer available.
It has been used quite a lot for unsupported porposes, causing many issues, support questions and other problems.
If you run Home Assistant, please be aware that running additional containers is not a supported use-case and will trigger your system to be flagged as unsupported as well.
If you need to install other software with Home Assistant, your best bet is to run home assistant container, or install Home assistant in a VM so you can run other software outside the vm
ah ok, thnx for info
is there an easy way then now to use a macvlan network? i want to run a specific local addon, but it needs to get an IP address of my router instead of the host network
What is the addon you want to run on a macvlan? Is it one you install through the supervisor (Ie an “official” or community Home Assistant addon), or something you are installing outside Home Assistant through Portainer?
Also, what is your current install method and hardware you are running Home Assistant on?
This portainer addon probably made it fairly simple to add a MACVLAN network, but without it, it’s going to be more difficult to create one unfortunately. I’m assuming you will have to install the full Home Assistant (Hassio) in a VM, and then docker (with or without portainer) outside of the VM to create a docker MACVLAN network. The other option is install docker with or without portainer, and use Home Assistant container, but you will lose the addon store and need to install the equivalent docker addons yourself. I actually run Home Assistant container and I can continue using the docker version of Portainer just fine - see my post here -
One of the reasons I run Home Assistant container is because it gives me more control over the install, lets me install anything else I want on the same machine, and I’m not impacted by the developers decisions to change or pull an addon just like they did here. If you can manage docker almost every addon has an equivalent full version you can install in docker yourself, without the supervisor (ie Node Red Installing Node Red in Docker for Home Assistant | by Jordan Rounds | Medium Zwavejs2mqtt https://zwave-js.github.io/zwavejs2mqtt/#/getting-started/docker , and zigbee2mqtt Getting started | Zigbee2MQTT). More control over the system means more work though.