This continuing unhealthy nonsense;
Portainer gets banned
Now means I can’t upgrade Core.
Anyone have a workaround to keep using Portainer and upgrade Supervisor beyond 2022.09?
Removing Portainer isn’t an option.
If removing Portainer isn’t an option, you may need to switch from Home Assistant Supervised to Home Assistant Container.
You will gain complete control over whatever containers you wish to install. However you will lose some of the convenience of Home Assistant Supervised (such as Add-ons).
Thanks, but yeah that’s a no-go route for the reason you’ve mentioned.
- Make the other non-portainer images you use into addons by making a simple configuration file that basically just references the image you’re already using. Then install and manage them from HA UI and remove portainer
- Put HAOS in a VM and restore a backup there. Then add another VM with docker and a docker compose script to start the other software you need. Or use portainer there if you really want to I guess.
1 Like
Thanks, I’ll try option 1 for some non-critical images and see how that goes.
I’m thinking I could run up Portainer with a different name perhaps to evade big-brother?
I’m not in a position to answer that. Perhaps you should direct your question to CentralCommand. It’s my understanding he contributes to the development of the Supervisor.
I guess we’re talking on two different threads now but all checks can be ignored:
# ha res check options -h
This command allows to apply options to an specific check managed by the system.
Usage:
ha resolution check options [flags]
Aliases:
options, option, opt, opts, op
Examples:
ha resolution check options [slug]
Flags:
--enabled Enable/Disable check on the system (default true)
-h, --help help for options
Global Flags:
--api-token string Home Assistant Supervisor API token
--config string Optional config file (default is $HOME/.homeassistant.yaml)
--endpoint string Endpoint for Home Assistant Supervisor (default is 'supervisor')
--log-level string Log level (defaults to Warn)
--no-progress Disable the progress spinner
--raw-json Output raw JSON from the API
But just be aware things are only considered to be a bug if they are reproduced on a supported system. So if you report an issue in any of the HA repos that you encountered with your system configured like this you’ll be asked to reproduce it on a supported system to be considered for further investigation as a bug.
Can you please elaborate?
I get the following error:
Error: The supplied check slug is not available
I concluded I didn’t want to remove the checks wholesale, so instead I’ve used a different name for the image and container. See below how to do this, but do so knowing this is circumventing the check for portainer being present along with all of the well-intentioned reasons for it now being there.
Run Portainer under another name
sudo docker stop portainer
docker rm portainer
docker pull portainer/portainer-ce:latest
docker tag portainer/portainer-ce:latest iamnotportainer
docker run -d -p 8000:8000 -p 9443:9443 --name iamnotportainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data iamnotportainer
docker rmi portainer/portainer-ce
Check that the image/container are now names as expected
docker ps
docker images -a
Any errors on pulling the image, try these:
sudo systemctl daemon-reload
sudo systemctl restart docker
Also check DNS is working - edit this file:
/etc/resolv.conf
Add this line:
nameserver 8.8.8.8
Check Home Assistant is healthy again.
4 Likes
Thank you for this! However, your run command wasn’t working for me with the ports you used, not sure why.
I ended up using these instead:
docker run -d -p 9000:9000 -p 8000:8000 --name iamnotportainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data iamnotportainer
2 Likes
Yep, 9000 are the ‘old’ portainer ports, 9443 are the ‘new’ ones depending on the install you have.
I created a portainer v2 add-on for supervised HA in Feb 2021.