hassio-addons/addon-portainer

Portainer - Home Assistant Community Add-ons

Home Assistant Community Add-on: Portainer

Manage your Docker environment with ease.

About

Portainer is an open-source lightweight management UI which allows you to easily manage a Docker host(s) or Docker swarm clusters.

It has never been so easy to manage Docker. Portainer provides a detailed overview of Docker and allows you to manage containers, images, networks and volumes.

📚 Read the full add-on documentation

DISCONTINUED

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.

WARNING 1

The Portainer add-on is really powerful and gives you access to virtually your whole system. While this add-on is created and maintained with care and with security in mind, in the wrong or inexperienced hands, it could damage your system.

WARNING 2

The Portainer add-on is meant for debugging Home Assistant and its containers. It has not meant or designed for managing or deploying your custom software or third-party containers.

Home Assistant DOES NOT SUPPORT running third party containers on Home Assistant OS or Supervised installation types. Ignoring this, will render your system as unsupported!

Support

Got questions?

You have several options to get them answered:

• The Home Assistant Community Add-ons Discord chat server for add-on support and feature requests.
• The Home Assistant Discord chat server for general Home Assistant discussions and questions.
• The Home Assistant Community Forum.
• Join the Reddit subreddit in /r/homeassistant

You could also open an issue here GitHub.

Contributing

This is an active open-source project. We are always open to people who want to use the code or contribute to it.

We have set up a separate document containing our contribution guidelines.

Thank you for being involved! 😍

Authors & contributors

The original setup of this repository is by Franck Nijhof.

For a full list of all authors and contributors, check the contributor's page.

We have got some Home Assistant add-ons for you

Want some more functionality to your Home Assistant instance?

We have created multiple add-ons for Home Assistant. For a full list, check out our GitHub Repository.

License

MIT License

Copyright (c) 2018-2021 Franck Nijhof

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

addon-portainer's Issues

No containers

Problem/Motivation

On the "Home" page I can see containers
But clicking on them takes me to the primary dashboard where there are no containers listed.

Expected behavior

I expected a list of containers.

Actual behavior

No containers listed

Steps to reproduce

I installed it and using the default configuration.

Proposed changes

Enhancement: Add port mapping 8000 option

Problem/Motivation

To manage edge agent endpoints portainer must export port 8000

Expected behavior

An option to map ports 80/9000 and 8000

Actual behavior

Only possible to map 1 port

Steps to reproduce

Configure an "Edge agent" in portainer endpoints where you will see the message "The agent will communicate with Portainer via https://192.168.69.1:9000 and tcp://192.168.69.1:8000"

Proposed changes

Create an additive port mapping option with default behavior not exposing the port

Container is missing

Problem/Motivation

I just use this addon for the first time but I see some weird in dashboard compare to container page

Expected behavior

I have 12 container up and running but in container page it show only 1

Actual behavior

This image is showing correctly number of running containers

But when I go inside, it show only 1 container

Steps to reproduce

1. I use hassio os with raspberry pi 4
2. install addon and disable protected mode

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

docker image

cant download more then 1GB Docker image and cant upload it to

Cant install on latest version: This add-on is not available on your system.

Problem/Motivation

I can not install this on a recent version of hassio

Expected behavior

I should be able to install it

Actual behavior

Steps to reproduce

Run hassio > 0.90 and this is not installable

Cannot pull any image.

Problem/Motivation

I am attempting to install homebridge in a docker container. I also tried installing lighttpd. Both give a red "Failed to pull image" when trying to download them.

Steps to reproduce

(How can someone else make/see it happen)

On a clean install of the home assistant image install the portainer addon, disable protected mode as instructed and start the container. Access the webui and try to pull any image but specifically lighttpd and homebridge. Why do I want homebridge when home assistant has homekit? I have added all my broadlink rm pro devices AND my switchmate bluetooth devices to homebridge and they work great. I saw no EASY method to integrate them into home assistant and it makes no sense to run two pi's just so homebridge and home assistant can run on the same lan.

Thank you for your time.

Portainer addon starts but dies immediatly when visiting the portainer page

Problem/Motivation

Just installed HassOS 5.11 on a Raspberry Pi 4. Installed the Portainer addon, I can start it but as soon as I visit the Portainer page the addon dies and I am asked to start it again.

Expected behavior

Portainer addon starts

Actual behavior

Portainer addon does not start

Steps to reproduce

1. Start portainer addon
2. Navigate to the Portainer menu item in the sidebar

Logs

Feb 21 16:56:19 homeassistant hassos-supervisor[881]: 21-02-21 16:56:19 INFO (SyncWorker_3) [supervisor.docker.interface] Cleaning addon_a0d7b954_portainer application
Feb 21 16:56:21 homeassistant hassos-supervisor[881]: 21-02-21 16:56:21 INFO (SyncWorker_3) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/portainer/aarch64 with version 1.4.0

Update to Portainer 2.0

When can the update to version 2.0 be expected?

https://github.com/portainer/portainer

Re-add the ability to set a custom port in the netwerksettings

Problem/Motivation

On multiple occasions I was able to debug and fix Home Assistant docker issues with Portainer. Of course I could have used docker cli, but Portainer is very powerfull and just easier 😄
Why can't Ingress and the direct access support coexist? I understand this would be fine for some add-ons, but Portainer is just too important for debugging. Because now, if Hass is down, Portainer is unreachable.

Proposed changes

Can you please (re)add the ability to map a custom port (like 9000) to Portainer?

Thanks 😄

Duplicate of #4

Problem/Motivation

Portainer does not start, same exact error as before: #3 #4 #5. #4 claims to be working and is closed, but that is not the case.

-----------------------------------------------------------
 Hass.io Add-on: Portainer v0.4.2
 Manage your Docker environment with ease
 From: Community Hass.io Add-ons
 By: Franck Nijhof <[email protected]>
-----------------------------------------------------------
 amd64 / HassOS 1.13 / HA 0.90.2 / SU 150 / stable
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing... 
INFO: You are running the latest version of this add-on
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 10-requirements.sh: executing... 
FATAL: The configured certfile is not found
[cont-init.d] 10-requirements.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing... 
-----------------------------------------------------------
                Oops! Something went wrong.
 
 We are so sorry, but something went terribly wrong when
 starting or running this add-on.

Expected behavior

portainer should be able to start and run

Actual behavior

fails to start, errors in log

Steps to reproduce

• Install portainer
• click start
• observe logs

Can't see containers

Problem/Motivation

When i open Portainer in have one Primary Endpoint. in the description it say that i have 15 (12 active) containers. (that sounds accurate)
When i open the endpoint dashboard i can only see two containers and they are both inactive.

Expected behavior

To be able to see and manage all containers that is installed via Homeassistant

Actual behavior

I can only see the 17 images and two inactive containers and 4 networks. no stacks or volumes vissible.

Steps to reproduce

Don't know if possible

Proposed changes

None

Log
[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] 00-banner.sh: executing...

---

Hass.io Add-on: Portainer
Manage your Docker environment with ease

Add-on version: 0.9.0
You are running the latest version of this add-on.
System: Ubuntu 18.04.3 LTS (amd64 / qemux86-64)
Home Assistant version: 0.105.5
Supervisor version: 201

Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.

[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] nginx.sh: executing...
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] portainer.sh: executing...
[cont-init.d] portainer.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[15:12:38] INFO: Starting Portainer...
[services.d] done.
2020/02/25 15:12:39 Templates already registered inside the database. Skipping template import.
2020/02/25 15:12:39 Instance already has defined endpoints. Skipping the endpoint defined via CLI.
2020/02/25 15:12:39 server: Reverse tunnelling enabled
2020/02/25 15:12:39 server: Fingerprint XXXXXXXXXXXXXXXXXXXXXXX
2020/02/25 15:12:39 server: Listening on 0.0.0.0:8000...
2020/02/25 15:12:39 Starting Portainer 1.23.0 on 127.0.0.1:9000
2020/02/25 15:12:39 [DEBUG] [chisel, monitoring] [check_interval_seconds: 10.000000] [message: starting tunnel management process]
[15:12:39] INFO: Starting NGinx...
nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)

Can't install container

Problem/Motivation

I was trying to install deepstack AI for blue iris integration on HASSIO

Expected behavior

container to be downloaded the deployed

Actual behavior

Error on Portainer, works in actual command line using docker pull

Steps to reproduce

same as
https://community.home-assistant.io/t/portainer-issue-with-creation-of-new-container/194757/20

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Portainer is not able to download extensions manifest

Problem/Motivation

Portainer is unable to download the extensions.json from internet.

(Why the issue was filed)

Expected behavior

Portainer should be able to download the json.

(What you expected to happen)

Actual behavior

Logs:

-----------------------------------------------------------
 Hass.io Add-on: Portainer
 Manage your Docker environment with ease
-----------------------------------------------------------
 Add-on version: 0.9.0
 You are running the latest version of this add-on.
 System: Debian GNU/Linux 10 (buster)  (armv7 / odroid-xu)
 Home Assistant version: 0.105.5
 Supervisor version: 201
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] nginx.sh: executing... 
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] portainer.sh: executing... 
[cont-init.d] portainer.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[08:26:28] INFO: Starting Portainer...
2020/02/20 08:26:33 [WARN] [exec,extensions] [message: unable to retrieve extensions manifest via Internet. Extensions will be retrieved from local cache and might not be up to date] [err: Get https://portainer-io-assets.sfo2.digitaloceanspaces.com/extensions-1.23.0.json: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)]
2020/02/20 08:26:33 [WARN] [exec,extensions] [message: unable to retrieve extension information from Internet. Skipping extensions update check.] [err: open /extensions.json: no such file or directory]
2020/02/20 08:26:33 Templates already registered inside the database. Skipping template import.

(What actually happened)

Steps to reproduce

I installed hassio, restored a snapshot, and got some DNS issues, but now, they are sorted out, as components are able to connect, also when I use the Web Terminal I am able to wget the json from the same url. For the same timestamp in the log, I do see a green entry in Pi Hole so the DNS lookup must have succeeded.

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

containers not showing correctly

I have installed the latest portainer supervisor addon. When I open it the home page Primary shows 0 stacks, 16 containers (15 open, 1 not open) and 16 images. When I then go to the summary page, it says I have 0 containers and 16 images. The containers page is blank. I am running a number of HA containers...and if I recall, portainer itself should show as a container.

I'm running Home Assistant supervised (core-2021.3.4) in a proxmox (6.3) VM using the debian 10 LXC and docker. Portainer 1.24.0

Even though it's a complex install and there are alternatives, the strange part is that clearly, portainer knows there are 16 containers on the home page, but then it doesn't show that they exist when you go further and try to show and/or work with them.

Portainer failing to start

Problem/Motivation

Installation seems to work fine. When starting portainer after adding some additional config info, the add-on won't start successfully.
Note: I have used the 'leave_front_door_open' option. Here is my config:
{ "log_level": "debug", "ssl": false, "certfile": "fullchain.pem", "keyfile": "privkey.pem", "hide_hassio_containers": false, "leave_front_door_open": true }

Expected behavior

Would expect it to start based on the documentation and steps followed.

Actual behavior

addon doesn't start and gives general 'oops' message. Rerunning with debug logging on I see the following. https://pastebin.com/K2aG6QN2

Steps to reproduce

I'm running hassio version 79.3 and installed the latest version of the portainer add-on 0.2.0.

Proposed changes

NA

Pastebin

{ "log_level": "debug", "ssl": false, "certfile": "fullchain.pem", " - Pastebin.com

Enhancement: Add mapping for web port (9000)

Problem/Motivation

To have the ability (like in many other addons) to access portainer locally without hassio (and authorization)

Proposed changes

adding port mapping for port 9000 being unset by default, so the user can decide wether the port should be opened or not

Can't embed Portainer as panel

Problem/Motivation

Due to X-Frame-Options: deny in Portainer it's not always possible to embed Portainer as an iframe panel.

Expected behavior

Users can embed Portainer in Hass.io

Actual behavior

Users can't

Steps to reproduce

Use portainer, try to embed it as an iframe panel in Hass.io
This does not work when using Tor or reverse proxy (sometimes)

Proposed changes

Update Portainer to upstream release 1.20.0 (portainer/portainer#2279)

i can't pull image after update to core-2021.6.x

I can't pull my self image or pull from App templates after update to core-2021.6.x

after create MySQL App templates, I got this error

no such image: MySQL:latest

in Supervisor Log

21-06-04 15:35:43 ERROR (MainThread) [aiohttp.server] Error handling request

i don't know docker.io server is down or problem is my DNS

Allow people to use without Ingress?

Could you allow this add-on to work without ingress? It's a grate thing but for something like Portainer it would be nice to have direct access back.

Can't update Portainer via HA Add-ons page

Problem/Motivation

The hass.io add-ons tab shows Portainer update is available from 1.0.0 to 1.1.0, however, the system cannot fetch the image.

Expected behavior

Package gets updated to 1.1.0

Actual behavior

Package does not get updated, the log shows the following errors:
20-04-01 14:21:37 INFO (SyncWorker_10) [supervisor.docker.interface] Update image hassioaddons/portainer-amd64:1.0.0 to hassioaddons/portainer-amd64:1.1.0
20-04-01 14:21:37 INFO (SyncWorker_10) [supervisor.docker.interface] Pull image hassioaddons/portainer-amd64 tag 1.1.0.
20-04-01 14:21:53 ERROR (SyncWorker_10) [supervisor.docker.interface] Can't install hassioaddons/portainer-amd64:1.1.0 -> 404 Client Error: Not Found ("no such image: hassioaddons/portainer-amd64:1.1.0: No such image: hassioaddons/portainer-amd64:1.1.0").
20-04-01 14:21:59 INFO (SyncWorker_18) [supervisor.docker.interface] Update image hassioaddons/portainer-amd64:1.0.0 to hassioaddons/portainer-amd64:1.1.0
20-04-01 14:21:59 INFO (SyncWorker_18) [supervisor.docker.interface] Pull image hassioaddons/portainer-amd64 tag 1.1.0.
20-04-01 14:22:16 ERROR (SyncWorker_18) [supervisor.docker.interface] Can't install hassioaddons/portainer-amd64:1.1.0 -> 404 Client Error: Not Found ("no such image: hassioaddons/portainer-amd64:1.1.0: No such image: hassioaddons/portainer-amd64:1.1.0").

Steps to reproduce

Click on "Update" button on hass.io Add-ons tab in Supervisor section

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

error-unable-to-retrieve-stack-list

I use an armbian system Under the docker environment, after I install portainer, I cannot view the stack, just like #32, but when I use ubuntu, everything is normal. homeassistant is the latest version, all are docker.

Unable to connect to the Docker endpoint

Problem

Clicking the 'primary' endpoint in 'Home' results in a failure so I am unable to see the container list.

Expected behavior

Clicking 'primary' shows me some/all of the 10 containers that the dashboard tells me are inside. I can then control them.

Actual behavior

A red message on the top right stating "Failure, Unable to connect to the docker endpoint". The page remains in 'home' view.

Steps to reproduce

Install Hassio, Install addons, Install portainer from addon store, disable protection mode, start portainer, open webUI, click 'Primary' endpoint'.
It has been this way for me for about 4 months. I have attempted uninstalling/reinstalling the portainer addon and changing SSL to 'false'.

Container stats error "invalid option"

Problem/Motivation

Container stats won't load

Expected behavior

I'd expect to see graphs and other stats

Actual behavior

It's giving me the following error: ps: ps: invalid option -- 'e'

Steps to reproduce

By clicking on one of these buttons:

or:

I'm running Hass.io on a Virtualbox VM on an Intel NUC.

Proposed changes

I found this topic: #3. Seems there was a fix before.

Support i386 architecture

Problem/Motivation

I'm running Home Assistant on my old netbook lying around with an atom processor. Looking at the specs it would be 3 times as powerful as a Raspberry Pi 3. I have a container for running ffmpeg RTSP to HLS to get audio feeds from security camera to Google Home Minis but it keeps stopping for some unknown reason so would be good to diagnose or restart it. I've heard about portainer on the Hass.io podcast which looks brilliant. What are the issues in supporting i386 architecture? If you're using the latest Docker CE, then that would be why since docker dropped support for i386 (boo!) In the end I used the legacy docker-io package on ubuntu which seems to be working.

Expected behavior

Install on my i386 netbook

Actual behavior

Can't install on the i386 netbook

Steps to reproduce

1. Install docker-io on a i386 machine
2. Install Hass.io on it
3. Try to install add on

Proposed changes

Perhaps define a different docker version/package/implementation so I could point it to use docker-io? If it's not possible don't worry.

Version is stale and old

Problem/Motivation

this addon installs a very old and stale version of this SW: 1.24 while we're on 2.5.1

Expected behavior

when I install and addon I expect it to have one of the latest versions of the SW, not a super old one.

Actual behavior

it installs a very old version of portainer

Steps to reproduce

Install it and verify the installed portainer is screaming at you begging to be updated.

Proposed changes

I tried to fix it my self opening a PR but it wasn't well accepted: #105

perhaps someone in the inner circle can open a more successful PR

Feature Request: Adding the AGENT_SECRET environment variable inside of the config

Problem/Motivation

Currently there isn't a good way to add the AGENT_SECRET inside of the portainer config. This Env Var allows you to be able to connect to remote portainer agents on external docker servers, only if the portainer agent also has the same shared secret.

This secret only takes affect when one the agent is restarted, because the agent utilized a trust first connection approach. This is bad if a malicious actor manages to connect to the agent first. To combat this they added the shared AGENT_SECRET env var, which will cause the agent to only pair with the first connection that has the shared secret as well.

As always thank you for all of your great work!

addon-portainer ce update?

Hi Franck,

This is not an issue, just a question and I have not seen anything relating this topic so forgive me if I am causing any duplicates.

Do you plan on updating this addon to use the latest portainer-ce?

Many thanks for your work,
Rob

Not starting

Installes on HASSIO: parse error: Expected string key before ':' at line 1, column 4

Hass.io Add-on: Portainer v0.2.0
Manage your Docker environment with ease
From: Community Hass.io Add-ons
By: Franck Nijhof [email protected]

armhf / HassOS 1.11 / HA 0.79.3 / SU 133 / stable

[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing...
INFO: You are running the latest version of this add-on
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 10-requirements.sh: executing...
[cont-init.d] 10-requirements.sh: exited 0.
[cont-init.d] 11-docker.sh: executing...
parse error: Expected string key before ':' at line 1, column 4
ERROR: Unknown HTTP error occured
[cont-init.d] 11-docker.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing...

            Oops! Something went wrong.

portainer not listed as an addon in the community repository

See this page:
https://github.com/hassio-addons/repository

There is no portainer it is missing.

GitHub

hassio-addons/repository

Community Hass.io Add-ons for Home Assistant. Contribute to hassio-addons/repository development by creating an account on GitHub.

Update portainer to latest release

Problem/Motivation

Update notification for Portainer CE, that a new release (2.6.0) is available

Expected behavior

(What you expected to happen)

Actual behavior

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

Can you please update the app to have latest portainer release?

PANIC: unprotected error in call to Lua API

Problem/Motivation

Portainer won't start

(Why the issue was filed)

Expected behavior

(What you expected to happen)

Actual behavior

[21:32:51] INFO: Starting Portainer...
2019/04/15 21:32:51 Starting Portainer 1.20.2 on 127.0.0.1:9000
[21:32:52] INFO: Starting NGinx...
PANIC: unprotected error in call to Lua API (bad light userdata pointer)
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing...
[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Remote endpoint port

Problem/Motivation

Would be a great feature if you could add more endpoints, i have several docker instanses.

Proposed changes

Add option to add more ports like port 2375

Pulling large images not working via Ingress

Problem/Motivation

It is not possible to pull larger images like "homegear/rpi-homegear:latest".

Expected behavior

The image should be pulled.

Actual behavior

I get an error that the image does not exist. This error only occurs when working via hassio Ingress. The function is working correctly when directly accessing your portainer instance via a defined port.

Steps to reproduce

1. Go to "Images" in the left hand menu in portainer.
2. Enter "homegear/rpi-homegear:latest" intro the image field.
3. Click "Pull the image".

Proposed changes

Pulling larger images should work via Ingress as well.

Portainer 2.0

Hi,

About this message on #55

Probably never, this add-on is most likely to be deprecated.
Portainer chooses a different path of 2.0, which is not a good direction for the add-on.

Originally posted by @frenck in #55 (comment)

Is there any alternative to this addon ?

Unable to install containers? (even from App Templates)

Problem/Motivation

Cannot install a container with default settings, even from a App Templates menu (e.g. File Browser) and receive this in log.

standard_init_linux.go:211: exec user process caused "exec format error",

Raspberry Pi 4
HassOS 3.11
Home Assistant 0.106.0b1
Portainer add-on 0.9.0

Expected behavior

Container to start up and not stop.

Actual behavior

Container stops a few seconds after starting.

Steps to reproduce

Add a new container
Run it

Proposed changes

Do not seem to know how to fix this.

Volume Mapping Bind

Problem/Motivation

Can't bind volumes up to the host. When creating a Volume for a container, you can usually Bind the volumes so that the data is mounted in the host. Whenever you do this through Hassio, you get "read-only filesystem".

Expected behavior

Be able to mount /share/myfolder from within a container.

Actual behavior

You get "read-only filesystem"

Steps to reproduce

Proposed changes

Allow passing a mount directory to the Hassio Portainer config that will be mounted to the Portainer container.

Portainer integration won't install

Problem/Motivation

Portainer won't install when "Install" is clicked in HA addon store.

Expected behavior

Expect to see "Installing..." and an activity swirly thing, then: Installed.... Start integration.... options

Actual behavior

Literally nothing happens - like the Install link/button is dead.

Steps to reproduce

Try to install portainer integration from the HA addon store.
currently running version HA core-2021.3.0 and HASSOS 5.12. Tried a HA restart.

Proposed changes

would be great if it could install when I click install.

Motioneye Container - standard_init_linux.go:219: exec user process caused: exec format error

Hi,

I need run container: https://hub.docker.com/r/jshridha/motioneye
Container must have parameter:

docker run -d --name=motioneye \
    --device=/dev/video0 \
    -p 8081:8081 \
    -p 8765:8765 \
    -e TIMEZONE="America/New_York" \
    -e PUID="99" \
    -e PGID="100" \
    -v /mnt/user/appdata/motioneye/media:/home/nobody/media \
    -v /mnt/user/appdata/motioneye/config:/config \
    jshridha/motioneye:latest

I add only ports and env: TIMEZONE, PUID, PGID but still show the same error:
standard_init_linux.go:219: exec user process caused: exec format error

---

My hardware environment

Raspberry Pi4 4GB
docker --version: 19.03.12
portainer: 1.3.0
Home Assistant 0.118.4
Hass.io: HassOS 4.17

Screen1:

Screen2:

Screen3 - env:

---

maybe I miss some options in: "Command & logging" or "Volumes" ??

--# NOTE1:
I noticed that after deploying container it creates "Host / volume" in:

-  /config
- /home/nobody/motioneye

but I dont have directory "nobody".
config is ok

--# NOTE2:
After deploying container i see in Container details:

CMD: /sbin/my_init

Is this really correct?

I need help :(

Strange ERROR's in the Supervisor logs

Problem/Motivation

There are a couple of ERROR's appearing in my Supervisor log related to Portainer. Portainer works normally as far as I know. I use LetsEncrypt and have HomeAssistant running on HTTPS, so maybe it has something to do with that.

Expected behavior

Not having ERROR's in my logs. :)

Actual behavior

20-11-13 08:14:32 ERROR (MainThread) [supervisor.api.ingress] Stream error with http://172.30.33.1:1337/api/motd: Cannot write to closing transport

20-11-13 09:22:15 INFO (SyncWorker_4) [supervisor.docker.addon] Starting Docker add-on hassioaddons/portainer-amd64 with version 1.3.0

20-11-13 09:22:15 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.1:1337 ssl:default [Connect call failed ('172.30.33.1', 1337)]

20-11-13 09:22:15 INFO (MainThread) [supervisor.api.security] /host/info access from a0d7b954_portainer

Steps to reproduce

Just using Portainer as normal.

Proposed changes

No clue, as I am not sure where it's coming from.

Describe functionality and purpose

Problem/Motivation

The Github page does not make it clear what this add-on does and when you would need it

Expected behavior

Before installing it's not clear what the interaction between Portainer and HomeAssistant is, or what the goal/benefit is

Proposed changes

Describe what order to install these components in (e.g. Portainer first, then Hass in docker, then add-on, in order to ........?)

Enhancement: Add mapping for port 9000

Problem/Motivation

When setting up portainer to work with edge agents, I came across the issue that the HTTP port for portainer is not exposed.
Unless I can supply authentication for homeassistant via the portainer agent (which I think is impossible) I need this port mapping alongside the ingress implementation.

Expected behavior

The ability to specify the HTTP port in the addon screen

Actual behavior

Only port 8000 can be specified

Steps to reproduce

Open addon settings

Proposed changes

Please add the mapping for port 9000 again to make use of edge agents.

hassio_observer not automatically filtered out

Problem/Motivation

Adding the Observer to hassio needs an improvement on the filtering of containers in this plugin

Expected behavior

hassio_observer not available in Portainer container listing

Actual behavior

It shows up.

Steps to reproduce

In my case: open portainer from home assistant menu and look in the containers running overview

Proposed changes

extend the filter

Client version too new api level 139 vs 140

Problem/Motivation

Cannot pull or import an image oznu/homebridge

Expected behavior

Successful import of tar file or image pull

Actual behavior

Error message and no image found

Steps to reproduce

Attempt to pull the image

Proposed changes

Fix api version mismatch

Cannot access REST api

Problem/Motivation

I am unable to do POST/GET requests on the Portainer API.
HA 0.97.0
Portainer 0.7.4
Startup log:
[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] 00-banner.sh: executing...

Hass.io Add-on: Portainer
Manage your Docker environment with ease

Add-on version: 0.7.4
You are running the latest version of this add-on.
System: HassOS 2.11 (armv7 / raspberrypi3)
Home Assistant version: 0.97.0
Supervisor version: 184

Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.

[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] nginx.sh: executing...
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] portainer.sh: executing...
[cont-init.d] portainer.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[11:27:31] INFO: Starting Portainer...
2019/08/29 11:27:31 Templates already registered inside the database. Skipping template import.
2019/08/29 11:27:31 Instance already has defined endpoints. Skipping the endpoint defined via CLI.
2019/08/29 11:27:31 server: Reverse tunnelling enabled
2019/08/29 11:27:31 server: Fingerprint a6:68:6e:ca:69:5a:df:8f:08:ed:97:59:91:a8:8d:9c
2019/08/29 11:27:31 server: Listening on 0.0.0.0:8000...
2019/08/29 11:27:31 Starting Portainer 1.22.0 on 127.0.0.1:9000
2019/08/29 11:27:31 [DEBUG] [chisel, monitoring] [check_interval_seconds: 10.000000] [message: starting tunnel management process]
[11:27:31] INFO: Starting NGinx...
nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)

Expected behavior

Able to access the Portainer API

Actual behavior

I use Postman to test the api. When I try to obtain a token via http://:/api/auth (POST) with Username/Password as JSON body using my HA user/password I always get 401 in return. It seems that the HA authentication is NOT used when authenticating via the API (or /api/auth endpoint).
Using endpoint /api/endpoints (GET) using a HA long life token (Header Authentication:Bearer ) doesn't work either. Tried to use the tokens that are passed when using webui but doesn't work either (makes sense).
Even tried the leave_frontdoor_open option in config file, then the /api/endpoints works without authentication but no container info is returned.

Steps to reproduce

Install Portainer addon.
Set a port in Network tab.
Start Portainer.
Try to do a POST request on /api/auth or GET request on /api/endpoints

Proposed changes

Describe how to use the Portainer API.

GitHub

openresty/luajit2

OpenResty's Branch of LuaJIT 2. Contribute to openresty/luajit2 development by creating an account on GitHub.

OpenResty - Download

Cant see any Container in Portainer on Hassos 5.10

when is login to portainer i can see 15 containers running on the homepage

but when i go to containers, there are no containers visible

Container Stats Fails

Problem/Motivation

STATS function is broken

Expected behavior

Showing Container CPU/Memory Stats

Actual behavior

Get Error Message: Error running ps: exit status 1

Steps to reproduce

Point to container, and click stats icon.

Feature Request: Dashboard as entry point

Problem/Motivation

When I used Portainer with the standard docker image, it opened the dashboard first. With the Portainer Hass.io addon it starts with "home". So I have to select the primary endpoint first.

Proposed changes

I don't know if it's possible to go to the primary dashboard instantly, but it would be more convenient for most of the users (I think most hass.io users only have one endpoint).

Regards,
Nico

DahuaVTO2MQTT Docker - install error

Problem/Motivation

I am trying to install the DahuaVTO2MQTT Docker within the HA add on Portainer
(https://community.home-assistant.io/t/dahua-vto-to-mqtt-broker/169781)

I followed the instuctions in this video- https://www.youtube.com/watch?v=-oOP38KpvfE

The container creates successfully , however i cannot see the VTO events within HA
I can see these error in the container logs.

standard_init_linux.go:219: exec user process caused: exec format error,
standard_init_linux.go:219: exec user process caused: exec format error,
standard_init_linux.go:219: exec user process caused: exec format error,
standard_init_linux.go:219: exec user process caused: exec format error,
standard_init_linux.go:219: exec user process caused: exec format error,
standard_init_linux.go:219: exec user process caused: exec format error,
standard_init_linux.go:219: exec user process caused: exec format error,
standard_init_linux.go:219: exec user process caused: exec format error,
standard_init_linux.go:219: exec user process caused: exec format error,
standard_init_linux.go:219: exec user process caused: exec format error,
standard_init_linux.go:219: exec user process caused: exec format error,
standard_init_linux.go:219: exec user process caused: exec format error,

Expected behavior

I am expecting to see the events published within HA

Actual behavior

I do not see anything within HA events or in the Mqtt broker.

Steps to reproduce

1. Running HA OS 5.10
2. Mosquitto broker 5.1
3. Portainer 1.24.20 add on
   Protection Mode off
   no configuration changes
4. create container using below Variables
   version: '2'
   services:
   dahuavto2mqtt:
   image: "eladbar/dahuavto2mqtt:latest"
   container_name: "dahuavto2mqtt"
   hostname: "dahuavto2mqtt"
   restart: always
   environment:
   • DAHUA_VTO_HOST=vto-host
   • DAHUA_VTO_USERNAME=Username
   • DAHUA_VTO_PASSWORD=Password
   • MQTT_BROKER_HOST=mqtt-host
   • MQTT_BROKER_PORT=1883
   • MQTT_BROKER_USERNAME=Username
   • MQTT_BROKER_PASSWORD=Password
   • MQTT_BROKER_TOPIC_PREFIX=DahuaVTO
   • DEBUG=False

Proposed changes

Hoping somebody can help/provide direction.

Thanks

configuring virtual_host

In case you have an alternative hostname to access Portainer (e.g., DuckDNS), it would be nice if you can specify it in an option.

Perhaps there already is a way to set this?

I want to place Portainer in an iFrame, but having SSL issues because I cannot run Portainer on my domain, only accessible via ip:port.

EDIT: My understanding was incorrect.

Primary menu is not showing

Problem/Motivation

I can't see the Primary menu list in the Portainer add on. I am trying to add a new container and I can

Expected behavior

See the Primary menu list so i can add a container

Actual behavior

Primary menu list is not visible so I can't add a container

Steps to reproduce

I simply installed the add on as expected: Install > disable protection mode > start

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)