Updating images from stacks created in Portainer

[zkvvoob]

Hello,

Is it important that all my docker compose stacks are created and managed in Portainer? The reason I'm asking is, when I ran dockcheck.sh just now and tried with one of the containers from which there appeared to be an update, I got an error:

Containers with updates available:
1) glances
2) grist
3) nextcloud
4) postgres
5) radicale

Choose what containers to update.
Enter number(s) separated by comma, [a] for all - [q] to quit: 1

Updating container(s):
glances

Now updating (1/1): glances
latest-full: Pulling from nicolargo/glances
fe07684b16b8: Already exists
0b37e7f71dd6: Pull complete
d51beea43a06: Pull complete
06fa3698e982: Pull complete
5d2c022f16ed: Pull complete
20e9783d9713: Pull complete
4f4fb700ef54: Pull complete
8b6cb7827efd: Pull complete
07173c25c612: Pull complete
Digest: sha256:df769f622f0220a9c53653a9e09dbaf2e2a562191cae5e8c36d1b94da98f462b
Status: Downloaded newer image for nicolargo/glances:latest-full
docker.io/nicolargo/glances:latest-full

Done pulling updates. Recreating updated containers.
./dockcheck.sh: line 577: cd: /data/compose/49: No such file or directory

Path error - skipping glances

/data/compose/49 is where Portainer saves its stacks.

[mag37]

As per Known Issues

Not working well with containers created by Portainer.

And Issues:portainer label.

There's a bunch of issues with trying to run dockcheck with Portainer-managed containers, I've not found a good way of solving this. People (and I) have been trying different odd solutions without something working consistently.