This is my first time using CoreELEC. After installing linuxserver’s docker and portainer extensions, “portainer container killed” notification pops up every one to three minutes.
A few days ago I’ve found the Events Tab on portainer page, it shows the container been “killed” every 1 to 10 seconds, then stop for a few minuite.
But the container does not actually been killed, I can access the portainer webpage seamless.
Turning on debug mode and searching for /storage/.kodi/temp/kodi.log find nothing useful information.
I’ve upgraded from 19.20-rc2 to 19.2-rc3, but seems the same. I’ve tried reinstall docker and portainer extensions, but nothing change.
A bit of history on this. To be honest, I’ve stayed on 9.2 because I don’t understand the implications and can’t risk the proper operation of Plex thro docker.
I’ll follow this thread in the hope it gets sorted.
I don’t know what you are doing, if a docker container is generating a lot of notifications it means that something is wrong in the creation / configuration of the docker container. Delete the container, review the parameters, and create the container again, like this until everything works fine.
I don’t trust CE container creation addons because in the past I saw a lot of errors, that’s why I always use SSH commands. My portainer creation command is:
If you just install docker using the addon, then disable the addon, then your services/containers, everything works great and no kill messages.
This may mean you don’t get updates to docker/the docker addon, but you can do those manually (if you need to - as it is really just a service runner here, if it is all working, it do you really need updates at all?)
Basically just use the addon to install docker, then remove the kodi side of things and use docker fairly much as normal, works well…have been using it with 19 for a few months now without issues (after I disabled the service part of the addon on).
Are you saying remove the three lines from the addon.xml files for docker, updater and plex that vpeter suggested? It stops the kills, I know, but I wasn’t sure if something would break if there was an update. I think you’re telling me that I just won’t get them.
How would I go about installing an update manually in these circumstances? I can run commands in SSH but I don’t understand what they mean.
I have been using docker for over a year with no problems. I know that it is difficult to understand how it works but it is essential to study it in order to use it. My opinions are as follows:
The addon that starts the docker service works very well and you don’t have to modify anything, not even the notification settings.
Avoid using any other docker-related addon, if something doesn’t work right you won’t know if it’s your fault or the addon’s fault.
Install the portainer service first, this allows you to manage the rest of the dockerized services through the web on port 9000.
Learn to use the SSH command line to install / test new dockerized services, for this consult the websites hub.docker.com and linuxserver.io, you can learn how they are used and they will even take you to the github site of the author of the docker image. In summary, I propose that you act as you would with an entware service.
The portainer service allows updating the rest of the dockerized services, but I prefer to use the crazymax/diun service to do this automatically but with manual start, in this way I know immediately if everything continues to work well. For example, an unexpected update on the VPN server can cause an unsolvable crash if I am away.
Don’t forget to save the SSH command that started each of the docker containers, you may need it later, for this I use the /storage/.config/dockers directory. Also save the operating data of each docker container in the /storage/.config/dockers/<docker-container-name> directories. And finally, name each of the containers following the <relevant-port>-<container-name> criteria, to remember the port that each docker service uses.
All of that is fine and true, but docker with the use of Kodi profiles IS definitely broken. It’s by design - with Kodi 19, services are stopped and restarted with profile changes. This includes the docker addon and causes the kill messages.
I have some very complex docker setups going here and at work…it’s not the docker config or inexperience with it, it’s specifically the interrelationship between profiles and docker (in the case of my issue).
It is broken for years. For some it works, for some Kodi crashes, some has some different issues.
I think such system docker services should be manually edit to remove start/stop from Kodi and be just ordinary service. Only install/update should be done from Kodi. Of course this is little advance thing. But any little more heavy user could be capable to do that.
(Side point - I’ve used Kodi Profile for 13 years without much issue…as long as you use a Master profile for settings and then sub-profiles for your actual profiles, things work great. They get muddier if you use a main profile master profile, and a sub profile, as then settings tend to get confused…I think most folks start off with one main profile, then add more (which then gets confusing as they behave as sub profiles and inherit from that master profile) = when really it’s best to start with a main, empty profile, and create and actually use extra profiles - whilst leaving that main one there and alone).
I’d personally prefer if docker were wholly removed from Kodi - it just confuses things. Just have a little official install script to curl, that brings along docker and docker-compose.
But then I am quite comfortable with the shell so I suppose for GUI only users that’s no good…but if there were a little GUI runner that just ran that script as a one off (and maybe threw in Portainer for further GUI management of services) - that would work well I think.
