bachel

Thank you was freaking out for a seconde

Hi and thanks a lot for maintaining FolderView2 and continuing the original Folder View project! I’m using containers that run through another container’s network (e.g. --network=container:GluetunVPN). I’ve noticed an odd behavior: If I restart/rebuild the Gluetun container, only the dependent containers that are in the same Folder get rebuilt/restarted. Dependent containers that live in a different Folder (but use the same --network=container:GluetunVPN) are not rebuilt/restarted. Is this expected? Does FolderView2 currently detect cross-folder dependencies for container:<name> networking? Is there a way to “rebuild/restart all dependents” across folders, or could this be supported? Steps to reproduce (example): Gluetun container GluetunVPN. App A (Folder “Media”) with --network=container:GluetunVPN. App B (Folder “Downloaders”) with the same network mode. Restart/rebuild GluetunVPN from the UI. Observed: App A rebuilds/restarts (same Folder as Gluetun). App B does not (different Folder). Expected: All dependents using container:GluetunVPN rebuild/restart regardless of Folder. Apologies if this has already been discussed and I missed it — I just wanted to double-check if this behavior is known or intentional. Thanks again!

I have the same problem also docker uses latest but still shows update to 3.2