The add-on only works over ingress, and is indeed not externally available.
Suppose I modify the docker settings for the homeassistant container. Portainer is convenient for such changes. Now, how do I persist this change or backup the containerās new config (a docker-compose.yml would be great).
I looked in the compose directory where portainer stores its docker-compose.yml files, but it is empty.
I have confirmed the portainer container has a persistent disk dir mapped into it, /home/myname/portainer_data:/data
I needed to change the HA container config to map my zigbee usb stick device path, /dev/ttyACM0, into the container for ZHA.
Now I donāt know where this config change is persisted, and I fear it is not persisted at all to disk.
If this is the wrong way of modifying the HA containerās docker settings, please help me with the correct way.
Iām running the officially supported HA install with supervisor container.
I have searched for two days and cannot find any info on why my compose dir has zero docker-compose.yml files or how I should modify the HA containerās docker settings.
Thank you in advance for any help you can provide
If you use a supervised intally you donāt use docker compose at all and youāre right none of those settings will be persistent. You need to do that mapping in the ZHA addon settings.
hi, iāve tried to upgrade hassio from 32 bit to 64bit yesterday.
On the fresh install i installed portainer, as hassio addon. Then I try to create a new docker container(mbentley/omada-controller:latest-arm64, but i can pick any) and it doesnt work.
i get an error message in portainer : āobject not found inside the databaseā and the portainer log says : http error: Unable to proxy the request via the Docker socket (err=Object not found inside the database) (code=500).
I tried it twice with 2 different sd cards, am I doing something wrong or is it broken?
Hi there,
how do you guys backup container and volumes managed by via portainer only? Do you even Backup?
I only backup the config folder. You donāt backup containers. They are disposable.
You mean the portainer container /data folder? How do you backup? With an external script, cron based? Donāt you have non-disposable data in other containers?
Yes I use cron to back the config folder for all containers running from docker (except Home Assistant) Again, there is no data in the container itself. You should map persistent volume when you create the container and that is what you backup.
Iām also seeing this error, not sure how to work around it.
Same error here. Object not found. Brand new install of Portainer add-on on Home Assistant Core running on a NUC.
I think the current portainer addon 1.2.1 is broken. Version 1.2.0. works correctly on my NUC, while 1.2.1 gives the same error as mentioned.
I just tried to deploy seafile via portainer. I used this docker-compose.yaml (slightly modified) to create a new stack:
When trying to deploy, i just get this error:
Deployment error
Unable to deploy stack
When I remove the networks section (lines 43-44) and all other network entries (lines 11-12, 18-19, 40-41) it does deploy correctly. Anyone an idea, whats wrong with the network?
How do you install a specific version of Portainer via the HA addon store? Sorry, Iām new to HA. Thanks.
As far as I know, the only way to install an older version is restoring a snapshot backup. So this only works, if you have a backup of an older version.
I was just about to open an issue on the addons github, seems like frenck is already on it 
Take a look at https://github.com/portainer/portainer/issues/4125
Seems like this has high priority and will be adressed shortly. For now you should probably downgrade and wait for a version >1.2.1
1 Like
Iām having issues trying to create a container. Previously i had Home Assistant running on on a Virtual Box in Mac with Portainer installed with 3 other containers running.
Decided to move to Raspberry Pi 4B, when i try to create the same Container with images pulled from Docker Hub i get this:
[16:47:56] INFO: Starting Portainer...
[16:47:56] TRACE: bashio::fs.file_exists: /data/hidden
[16:47:56] TRACE: bashio::config.has_value: agent_secret
[16:47:56] TRACE: bashio::config: agent_secret
[16:47:56] TRACE: bashio::jq: /data/options.json if (.agent_secret == null) then
null
elif (.agent_secret | type == "string") then
.agent_secret // empty
elif (.agent_secret | type == "boolean") then
.agent_secret // false
elif (.agent_secret | type == "array") then
if (.agent_secret == []) then
empty
else
.agent_secret[]
end
elif (.agent_secret | type == "object") then
if (.agent_secret == {}) then
empty
else
.agent_secret
end
else
.agent_secret
end
2020/08/09 16:47:56 Warning: the --no-auth flag is deprecated and will likely be removed in a future version of Portainer.
2020/08/09 16:47:56 Warning: the --template-file flag is deprecated and will likely be removed in a future version of Portainer.
2020/08/09 16:47:57 Templates already registered inside the database. Skipping template import.
2020/08/09 16:47:57 Instance already has defined endpoints. Skipping the endpoint defined via CLI.
2020/08/09 16:47:57 server: Reverse tunnelling enabled
2020/08/09 16:47:57 server: Fingerprint ec:10:45:22:e6:f0:44:d6:53:68:47:e2:bb:4c:c5:36
2020/08/09 16:47:57 server: Listening on 0.0.0.0:8000...
2020/08/09 16:47:57 Starting Portainer 1.24.1 on 0.0.0.0:1337
2020/08/09 16:47:57 [DEBUG] [chisel, monitoring] [check_interval_seconds: 10.000000] [message: starting tunnel management process]
2020/08/09 16:49:15 http error: Unable to proxy the request via the Docker socket (err=Object not found inside the database) (code=500)
Isnāt that the same issue as described above? Itās being worked on, downgrade to portainer addon v1.2.0 to fix it
My bad didnāt read the last post. How do i downgrade add-on on home assistant?
The easiest way would be to restore a backup and only select the portainer addon, if you have 1.2.0 backed up
Ok thank you, not sure if i still have the backup for 1.2.0. Iāll have to check the dates.
Edit: Donāt have the backup with the previous release, guess Iāll have to wait for it to get fixed.