Slartybart
commented
1 year ago PS... Sorry if this isn't a bug, they seem to have changed the way of reporting issues.
Open Slartybart opened 1 year ago
Slartybart
commented
1 year ago PS... Sorry if this isn't a bug, they seem to have changed the way of reporting issues.
jlesage
commented
1 year ago What version of Docker are you using ? Can you look at log/engine_error.log and log/engine_output.log, under the directory you mapped to /config ?
Some users had issue when using an old version of Docker. See https://github.com/jlesage/docker-crashplan-pro/issues/423
Slartybart
commented
1 year ago I assumed it was a newer version of Docker, but I may have got it confused with the new ‘container Manager’. It seems to be 20.10.23-1413. It’s on a synology machine. I’ll try and pull the other logs, but I’m away from home. Thanks as ever.
Slartybart
commented
1 year ago jlesage
commented
1 year ago By Docker version, I was talking about the version of Docker itself, the one you get when you run docker version.
bdegeeter
commented
1 year ago I'm seeing this same issue on my unRaid system (v6.11.5). Here's the docker version info:
Linux 5.19.17-Unraid.
# docker version
Client:
Version: 20.10.21
API version: 1.41
Go version: go1.18.7
Git commit: baeda1f
Built: Tue Oct 25 17:56:30 2022
OS/Arch: linux/amd64
Context: default
Experimental: true
Server: Docker Engine - Community
Engine:
Version: 20.10.21
API version: 1.41 (minimum version 1.12)
Go version: go1.18.7
Git commit: 3056208
Built: Tue Oct 25 18:02:03 2022
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: v1.6.9
GitCommit: 1c90a442489720eec95342e1789ee8a5e1b9536f
runc:
Version: 1.1.4
GitCommit: v1.1.4-0-g5fd4c4d1
docker-init:
Version: 0.19.0
GitCommit: de40ad0Sorry for the delay... is this what you need?
Slartybart
commented
1 year ago This is with my Synology: I ended up deleting the container and starting again. When making the new container I assigned 'high privileges' to the new container, set the ports to 'host' rather than 'bridge'. Then of course I had to 'replace the existing device' and told it to skip files (so it wouldn't delete stuff missing from the drives I'm backing up), but so far so good..... I've only added one of the drives to be backed up initially, but it's already found most of the one drive I've added, and although slow, it's syncing files and blocks ok. Fingers crossed.
jasonmarkperez
commented
1 year ago I'm experiencing the same behavior since a Synology update and reboot docker version Client: Version: 20.10.23 API version: 1.41 Go version: go1.19.1 Git commit: 876964a Built: Wed Jun 14 06:00:26 2023 OS/Arch: linux/amd64 Context: default Experimental: true
jasonmarkperez
commented
1 year ago Downgrading to v23.06.1 seems to fix this for me, so I guess I'll hold at that version for now.
Current Behavior
Crashplan stuck in book loop.... Than ks as ever for help.
Expected Behavior
normal function
Steps To Reproduce
updated to latest and restarted crash plan
Environment
Container creation
restart with latest image
Container log
Container inspect
No response
Anything else?
No response