Possibility to update only containers without following composes files

[cyberspace458c4a8qze-bit]

Hi,

DockCheck is currently incompatible with Arcane or Dockge cause it use composes files to update and theses tools use relatives paths (that are not found by DockCheck so it fail everytime).

Can be possible to update containers by their properties and images ? instead of relying to composes files ?

Thanks

[mag37]

Greetings!
Sorry to hear its breaking with Arcane and Dockge. I know I've looked into recreating containers without pointing at the compose-file (due to Portainer having similar issues) but that I didn't come to any solutions.

I tried to look into it briefly now and couldn't see a way of doing it differently..

The issue is - if just doing the method

• Pull the new image, eg docker pull docker.io/amir20/dozzle:latest
• Restart with docker restart dozzle

Then the container wont use the newly pulled image. As it wont be recreated.

And I don't know if I'm missing something but I cant find a way to get it to recreate except for docker compose up -d which requires you either be in the directory of the compose or specify either the directory --project-directory or path to compose-file -f.

I would love if there was a solution to this and I'll try look into it further. If anyone got some idea I'm all ears!

[mag37]

I'll close this - I can't find way to sensibly get this working.

Hopefully a future container solution could bridge this gap (there's a PR currently if anyone want to test it: #261 ) and then bind those relative paths somehow.