mirror of
https://github.com/007revad/Synology_docker_cleanup.git
synced 2026-04-25 12:35:57 +03:00
[GH-ISSUE #10] Want to use cleanup after move, but run into error #3
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Synology_docker_cleanup#3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
@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 bashshebang 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.shOr
bash syno_docker_cleanup.shOr maybe you have installed dash via Entware?
@albertusQuelle commented on GitHub (Dec 26, 2024):
Thank you! That was the trick :)

But i cant find those little dot with .syno.bak reference
@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.