You added these after I posted. Originally, there were just 2 walls of undelineated text.
This is - at least - the third thread you've started this week on what amounts to the same docker issue, over & over. Numerous experienced members of the forum have devoted what must amount to hours of their time to your docker problems. You concluded the latest thread less than 24hrs ago, and now you've started yet another one up.
You did the same on threads around backups & encrypted drives, essentially coming back and asking the same question all over again despite people answering you and giving you perfectly good suggestions and fixes. Do you actually read all the help people post? It appears you don't.
Rather than presenting folks with a spaghetti of duplicated and failed docker containers, logs, weirdly formatted error messages and gui screengrabs (and then seemingly ignoring half of the suggestions as though they havent been made) why not start from basics and build up your containers one at a time. Be systematic. Get one working, test it, then move onto the next. That way, you have a chance of actually learning about how docker works, how mapped volumes work, how portainer interacts with them all, rather than poking a stick into random parts of the undifferentiated mess you've created in an attempt to chase down problems.
Does one respond to a tit-for-tat call out or not, as these generally run into diatribes and rarely will one convince the other of their perspective? Choosing yes, primarily because I respect this board a great deal and those who have been so helpful.I apologize if these posts frustrated you and hope, while you may not agree, you will have a more informed understanding from another perspective.
Spaghetti Wall
Think a good number of people reading will agree the posts were thoughtful, well formatted and written with consideration of the reader in mind; an easy read. One post had the logs pasted in, using a code tag which I expected would tidy up upon posting. That was not the case so I switched over the images for logs as makes for a tidier post. Interesting as I am now seeing for the first time the spoiler tag, something that might have worked on the earlier posts.
Note that I will refine posts for more clarity or information, partly because that is the encouraged behavior from the forum as posts are often auto merged...so timestamps aren't gong to give the true history of events cited by the post. I would even go back and place an official end post to assist in the topic closure and to say thank you.
Undelineated not.
Topics
It appears you view all of these posts as the same, categorized as all Docker. Docker is a large space, and each of the posts pertained to a different aspect of Docker. Updating, Portainer problem, stack crashing.
Backup & Encryption are Synology, not docker. I am not in this space day after day, ideally set and forget.
If something goes wrong, it is often the case more than one thing goes wrong. Yep, I google read posts, experiment and will post for input.
Effort
If one were to go back and review interactions I think one would be hard pressed to find a post to which I have not responded; even this one. One small post was not seen straight away and I responded to it as well. There were a few responses which seemed spot on and required a level of knowledge (low as it might be) to truly understand how to incorporate...so rather than risk exasperating the forum (which is what I'm seeing now) I needed to find other ways to fix which were understood different ways.
When learning about docker and its cool application I spent time learning, even had homebridge up and running. it was a few years ago now, can't say I'd have it all memorized. Everything worked...saved it all in multiple ways to prevent the amount time the project consumed. While I understand some segments, and 'how' mapped volumes work - I know I'd have a hard time remapping if starting from scratch. Too much went into the media set up to start over. Returning to the media set up and seeing it broken, it didn't seem like a recreation from scratch would be necessary. Updates and tweaks. Turns out it was some work, was frustrating but understand that better now for next time...AND...thankfully did not need to recreate everything from scratch.
The posts were in sequential order of the issues experienced. Docker services not working...discovered Portainer problem which became its own mini project (and post,) thought it was all good to go and then hit by the failing stack.
I humbly apologize to anyone frustrated by these posts
(primarily @Rusty who has been fantastic and clearly good person,) and truly appreciate the support those who have responded provided - even Fortran for possibly verbalizing what others have been thinking.
