Squid

Yeah, that was how things originally were, and there still is some adherents to it, but it is not encouraged for authors to do things like that. PM myself

You should undo whatever changes you did via the video and instead create the rootshare via Unassigned Devices (Main - Unassigned Devices with the plugin installed) Its the more official method than the manual editing of files etc to do this

I can replicate this on 6.10.3, but on 6.11.0-rc1 is seems to work fine. Can you update to the RC and see if this has already been fixed?

So I replicated this on 6.11 (still waiting on another update for 6.10) It's not a CA issue per se, but rather a docker tab issue where it isn't picking up that the container was actually updated (and updated via its own update routine - CA is nothing but a front end for the existing code in the docker tab) You can tell this because if you apply the update via docker, the total pull size will be zero and additionally a check for updates on docker will remove the Update being available. I'll look into it.

@bonienl

Thx. I have to wait for the next update to NetData to come through so I can retest (shouldn't be long. Usually updated every day)

Can you show me a screenshot

Probably the best place to ask is in their own forums, since they created both the template and the container.

You'd need to post your diagnostics

Which author (Plex official, LSIO, Binhex)?

If its the one from FoxMD, then not abandoned as its the official container for elasticsearch and they are the primary support for their own container. Did you run the command (and script) as detailed in the description?

Jun 15 09:11:11 PatricksNAS mcelog: failed to prefill DIMM database from DMI data Jun 15 09:11:11 PatricksNAS mcelog: Kernel does not support page offline interface Harmless and merely informative and safe to ignore. A BIOS upgrade (if available) might stop it from being logged

Not quite sure why it's not seeing the upgrade, but if you go to Settings - Notification Settings and disable (never check) for OS upgrades, then the Check For Updates button will appear

No worries. It just caught my eye and I went "huh?"

Not that I pay much attention to binhex's threads as he's great at supporting them, but I do have a question Why are you changing the container port? The container is running as bridge which means that you generally leave the container port alone (8080) and simply edit it to change the host port (to 8088) There's no conflict by having multiple containers all listening internally on 8080 as that's what the port mapping is supposed to do. The way that you're doing this means getting into the container's UI (which is still internally on 8080, but no port mapping now available for it), telling it to listen instead on 8088, deleting and adding the port (which you've done) in the template, and also changing the WebUI entry in the template to reflect now 8088 instead of how it was originally set (which works no matter how you map the port) This BTW is why on the template you cannot edit the container port number and have to instead delete and re-add

If the docker run command fails (and it says why when the command gets executed), then for all intents and purposes the installation failed, so the app will disappear from the docker tab because it's no longer actually installed.

Yes, you can safely uninstall and then reinstall. If the flash drive is confused, then you may also need to delete /plugins/community.applications on the flash

You can set Fix Common Problems to avoid disk spinups. And if this is happening constantly, then you've got FCP running way to often. Daily is more than sufficient.

Troubleshooting mode hasn't particularly existed in FCP for a couple of years now

This is my best guess as to what's tripping it: Jul 22 06:52:20 Plexy mcelog: Kernel does not support page offline interface and you should be good to ignore it.

"Container Size" on the docker tab - better than docker ps as it'll also include the log size

cp /var/log/syslog /boot/syslog and then upload the syslog from the flash Ideally, you would diagnostics and then upload the zip file that'll get stored within /logs on the flash drive

Search for piHole

With an OS that old, have you tried different machine types or using SeaBIOS?

You need to post your diagnostics and specify what share(s) you're seeing this on.