Welcome to the forum @ptruman
I split your post into a new topic because it wasn’t clear it was a new bug in 18.104.22.168, and discussing every support request on the release note topic is way too unreadable. If it’s a 22.214.171.124 bug, a note can be added.
Was all previously working? If so, on what release? Is the Docker from duplicati, linuxserver, or elewhere?
What does “restore/repair” mean? They are separate operations.
Please clarify “get nothing” and “nothing shows”. Is there a log for that use? Also check About → Show log -->Stored, although usually what goes there is errors on backups. Other operations are better at making a log file in the per-backup logs. That doesn’t mean all detail you’d want is there though. Which case is this?
Job logs typically show a condensed warning format with the first line. It’s a nice summary, but lacks detail.
About → Show log --Live --Warning (or a log file) can catch detail, but you might have to click on some line.
You might also have had a problem after the backup itself. For example, a problem in sending a report of a successful backup is not an unsuccessful backup (so log will be fine), but it might make you a GUI popup.