[GH-ISSUE #10] Want to use cleanup after move, but run into error #3

Closed
opened 2026-03-04 19:25:37 +03:00 by kerem · 3 comments
Owner

Originally created by @albertusQuelle on GitHub (Dec 25, 2024).
Original GitHub issue: https://github.com/007revad/Synology_docker_cleanup/issues/10

Hi,
after moving to the SSD my containers start failing (some reason like here so i wanted to use this script to cleanup.

image

Originally created by @albertusQuelle on GitHub (Dec 25, 2024). Original GitHub issue: https://github.com/007revad/Synology_docker_cleanup/issues/10 Hi, after moving to the SSD my containers start failing (some reason like [here ](https://github.com/007revad/Synology_app_mover/issues/149#issue-2754045052) so i wanted to use this script to cleanup. ![image](https://github.com/user-attachments/assets/6bbbaf2f-da5f-4fb5-8b3a-4b71a6981d1f)
kerem closed this issue 2026-03-04 19:25:37 +03:00
Author
Owner

@007revad commented on GitHub (Dec 25, 2024):

You would get that error is the script is running sh instead of bash. So the shell is ignoring the #!/usr/bin/env bash shebang at the top of the script.

Are you CDing to the folder containing syno_docker_cleanup.sh and then running it as syno_docker_cleanup.sh?

You'd need to run it as ./syno_docker_cleanup.sh

Or bash syno_docker_cleanup.sh

Or maybe you have installed dash via Entware?

<!-- gh-comment-id:2561999908 --> @007revad commented on GitHub (Dec 25, 2024): You would get that error is the script is running sh instead of bash. So the shell is ignoring the `#!/usr/bin/env bash` shebang at the top of the script. Are you CDing to the folder containing syno_docker_cleanup.sh and then running it as `syno_docker_cleanup.sh`? You'd need to run it as `./syno_docker_cleanup.sh` Or `bash syno_docker_cleanup.sh` Or maybe you have installed dash via Entware?
Author
Owner

@albertusQuelle commented on GitHub (Dec 26, 2024):

Thank you! That was the trick :)
image

But i cant find those little dot with .syno.bak reference

image

<!-- gh-comment-id:2562955995 --> @albertusQuelle commented on GitHub (Dec 26, 2024): Thank you! That was the trick :) ![image](https://github.com/user-attachments/assets/e474ac0c-df7f-4b71-ae26-8cea3add39c5) But i cant find those little dot with .syno.bak reference ![image](https://github.com/user-attachments/assets/4565fa45-9bfc-44b1-ba8b-e83f8e6e850e)
Author
Owner

@007revad commented on GitHub (Dec 26, 2024):

I'm not sure what causes the .syno.bak containers but not everyone has them.

I should change the script to check if there are any .syno.bak containers and only show those instructions if there are some .syno.bak containers.

<!-- gh-comment-id:2563041308 --> @007revad commented on GitHub (Dec 26, 2024): I'm not sure what causes the <container-name>.syno.bak containers but not everyone has them. I should change the script to check if there are any <container-name>.syno.bak containers and only show those instructions if there are some .syno.bak containers.
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Synology_docker_cleanup#3
No description provided.