mirror of
https://github.com/007revad/Synology_Docker_Export.git
synced 2026-04-25 04:25:47 +03:00
[GH-ISSUE #5] Running the script from another volume? #1
Labels
No labels
bug
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_Export#1
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 @tchit on GitHub (Oct 12, 2024).
Original GitHub issue: https://github.com/007revad/Synology_Docker_Export/issues/5
Hello,
My DS720+ drive is corrupt and in read-only.
I would like to save my Docker configurations for convenience and it is my understanding that it’s all in /volume1/@docker/
My issue is that when using SSH and sudo -i to access this folder, when I use the ls command to see the folder’s content I am met with this error when I enter /volume1/ :
Ls: reading directory « . » : Input/Output error
Someone told me about this script and it looks like it does exactly what I need in terms of saving all docker configs but I can’t install it on the Volume1 that holds my docker content since it’s read-only. Is there a way to start this script from another volume?
thanks
@007revad commented on GitHub (Oct 12, 2024):
You can run the script from a USB drive or thumbdrive.
Docker or Container Manager needs to be running for the script to work. Is Docker or Container Manager running?
And you'd need to edit line 70 to change it from this:
to match your USB1 or USB2 etc like:
You'd also need to backup your docker shared folder, which is usually
/volume1/dockerif you don't already have a backup of it.Do you have snapshots enabled?
ls: reading directory « . » : Input/Output errororls: reading directory . : Input/Output errorcan be caused by a hardware issue (damaged RAM or hard disk). It can also mean a damaged file system or a driver bug.Is the system partition read only as well? Does
ls /var/packageswork?@tchit commented on GitHub (Oct 13, 2024):
Thanks for your answer. Unfortunately Container manager isn’t running. I guess I need to find another solution, if there is one…Next time I’ll do backups with your script!Le 13 oct. 2024 à 02:42, Dave Russell @.***> a écrit :
You can run the script from a USB drive or thumbdrive.
sudo -s /volumeUSB1/usbshare/syno_docker_export.sh
Docker or Container Manager needs to be running for the script to work. Is Docker or Container Manager running?
And you'd need to edit line 70 to change it from this:
ExportDir="${DockerShare}/docker_exports"
to match your USB1 or USB2 etc like:
ExportDir="/volumeUSB1/usbshare/docker_exports"
You'd also need to backup your docker shared folder, which is usually /volume1/docker if you don't already have a backup of it.
Do you have snapshots enabled?
ls: reading directory « . » : Input/Output error or ls: reading directory . : Input/Output error can be caused by a hardware issue (damaged RAM or hard disk). It can also mean a damaged file system or a driver bug.
Is the system partition read only as well? Does ls /var/packages work?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
@007revad commented on GitHub (Oct 13, 2024):
You can run https://github.com/007revad/Synology_app_mover v3.1.60 from a USB drive and backup Docker or Container Manager to the USB drive. You'd need to have enough space of the USB drive.
@tchit commented on GitHub (Oct 13, 2024):
Wow will try that tomorrow! Thanks a lot Le 13 oct. 2024 à 07:54, Dave Russell @.***> a écrit :
You can run https://github.com/007revad/Synology_app_mover v3.1.60 from a USB drive and backup Docker or Container Manager to the USB drive. You'd need to have enough space of the USB drive.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
@007revad commented on GitHub (Oct 13, 2024):
I would suggest using a Linux computer, or Linux boot disk, to format the USB drive in btrfs. If it's not btrfs important information may not get backed up, or the backup may fail with error saying failed to backup
@docker.@tchit commented on GitHub (Oct 13, 2024):
I have disabled my raid setup and have a volume2 with a clean DSM install. I suppose I can do the operation from that volume?Thanks a lot Le 13 oct. 2024 à 08:13, Dave Russell @.***> a écrit :
I would suggest using a Linux computer, or Linux boot disk, to format the USB drive in btrfs. If it's not btrfs important information may not get backed up, or the backup may fail with error saying failed to backup @docker.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>