Home Assistant Community Add-on: Portainer

About the author of this add-on

Hi there!

I am Franck Nijhof, and I have 30 years of programming experience, in many languages. I am using this experience to work on the Home Assistant project by giving back my knowledge and time to the open source community.

The add-on you are currently looking at right now was developed/packaged by me. It is not the only add-on I have created; there are many many more :wink:

However, I have a problem… I am an addict. A :coffee: addict that is. Lucky for you, I turn that C8H10N4O2 (caffeine molecule) into code (and add-ons)!

If you want to show your appreciation, consider supporting me for buying a cup of high octane wakey juice via one of the platforms below! :heart:

Sponsor Frenck via GitHub Sponsors

Support Frenck on Patreon

Enjoy your add-on, while I enjoy the brain juice. :coffee:

Thanks for all the :two_hearts:

…/Frenck

Join our Discord server Follow me on Twitter Flollow me on Instragram Follow me on GitHub Follow me on YouTube Follow me on Twitch patreon-icon

P.S.: In case you want to ask me a question: AMA (Ask Me Anything). Most of the time I am online at the Discord chat. (I go by @Frenck in there as well).

1 Like

Great work :slight_smile:

I got two bugs:

1/ The embedding into home assistant is not working for me (hass.io/resinOS, 0.77.3). I got the following error in log (my.costom.domain being redacted here) :
Refused to display 'https://my.custom.domain:9000/' in a frame because it set 'X-Frame-Options' to 'deny'.
It works great without iframe.

2/ When first starting the add-on with hide_hassio_containers: true and then rebooting with hide_hassio_containers: false, it doesn’t work (meaning, hassio containers don’t show). I had to manually delete the hidden containers in settings.

Side bug (but it’s probably a portainer one): hidden containers are still counted on the home screen:
portainer

Thx for the work done here!

1 Like

:tada: Release v0.2.0

Full Changelog

Changed

  • Adds Hassio API role to configuration
  • Upgrades base image to v2.3.0

Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck

Hi Frenk. Thank you for your great job…
I’m taking the following error when I try to install Portioner

18-09-27 21:54:00 INFO (SyncWorker_11) [hassio.docker.interface] Pull image hassioaddons/portainer tag 0.2.0.
18-09-27 21:54:02 ERROR (SyncWorker_11) [hassio.docker.interface] Can’t install hassioaddons/portainer:0.2.0 -> 404 Client Error: Not Found (“no such image: hassioaddons/portainer:0.2.0: No such image: hassioaddons/portainer:0.2.0”).

I’m running Hass.io on top of Dietpi, using Pine64 card.
Do you have an idea about my problem ?

I tried to run this addon with latest HASS (0.79.3) in docker on Debian 9.5 and get the error below with the default config. How can I debug this further, or any suggestions for a fix?

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.
 
 We are so sorry, but something went terribly wrong when
 starting or running this add-on.
 
 Be sure to check the log above, line by line, for hints.
-----------------------------------------------------------
2 Likes

:warning: Due to recent changes to Hassio, this add-on is currently broken and un-installable.

It will keep working for users who have it installed already, but new installations are currently impossible.

We are awaiting a change to the Hass.io panel / frontend to give users the power to use this add-on again.
At this point, there is nothing I can do.

Is this affecting any other add-ons that you know of? Daniel Welsh’s dropbox addon has stopped deleting files just since 0.79 as well… wondering if these are related at all…

Please ask that with the topic/author/repo/maintainer of the other add-on.

I have done that and also on github. I was interested if you were aware of any other addons with issues.

Yeah, I have the same problem with this Add-On - It does not start. Here below the logs.

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... 
-----------------------------------------------------------
 Hassio 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.10 / HA 0.79.2 / 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.
 
 We are so sorry, but something went terribly wrong when
 starting or running this add-on.
 
 Be sure to check the log above, line by line, for hints.
-----------------------------------------------------------
[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.

First of all:

This is displayed on top of each page, please use it. (I’ve edited your post now).

Second, please read a little before just dumping the problem. You would have found the answer to your problem just a view posts up…

Please ask that with the topic/author/repo/maintainer of the other add-on.

Thank you man for your warm welcome! I love when the people approach to new users with a solution mixed with a polite answer. I really appreciate it.
It was my first post but I encourage myself to learn fast about how communicate myself with the community without causing any troubles for my stupidity.
On the other hand I have read a lot in fact, but unfortunately, I didn’t find an answer that meets my expectations. Therefore I have decided to share it with the community.
This add-on has been working correctly to me till I have updated to a new hassio version. So, when you say issues with “new installations” - Updates are also included?
Thank you very much and sorry for the inconvenience!

Hmm interesting, “new installations” in this case are people who install this add-on for the first time.
Is that the case for you? Or did it work before?

It did work before.

@frenck, do you know the bug tracking the issue with hassio?

It is not an issue. This is caused by new features enabled in the backend, not available on the frontend. The frontend RFC can be found here:’

Frenk,
Also my problem (hereunder my post of some days ago) is due to the same issue you mentioned?
Thank you for support


I’m taking the following error when I try to install Portioner

18-09-27 21:54:00 INFO (SyncWorker_11) [hassio.docker.interface] Pull image hassioaddons/portainer tag 0.2.0.
18-09-27 21:54:02 ERROR (SyncWorker_11) [hassio.docker.interface] Can’t install hassioaddons/portainer:0.2.0 -> 404 Client Error: Not Found (“no such image: hassioaddons/portainer:0.2.0: No such image: hassioaddons/portainer:0.2.0”).

I’m running Hass.io on top of Dietpi, using Pine64 card.
Do you have an idea about my problem ?

The add-on CANNOT be used. Stop trying.

I’ve going to remove it from the add-on store to prevent more discussions and questions.

Thanks for removing it from the store - but unfortunately, just a bit too late for me. I just installed it 30 minutes ago, ran into the error and came here to find if others had the same issue.