[BUG] Error copy jpg files inside .storage during processing image

[sirhideo]

Describe the bug
Error copying jpg files inside .storage during doubletake processing image.
ENOENT: no such file or directory, copyfile './.storage/matches/397fa834-e9b7-4941-9eb2-2ef5ee541b56.jpg' -> './.storage/latest/unknown.jpg'

Version of Double Take
1.13.11.8-SHA7

Expected behavior
success copy latest.jpg to unknown.jpg? i don't know.

** docker-compose.yml
`version: '3.7'

volumes:
double-take:

services:
double-take:
container_name: double-take
image: skrashevich/double-take:latest
restart: unless-stopped
volumes:
- /opt/doubletake/storage:/.storage
ports:
- 3000:3000
`

Hardware

• amd64
• Ubuntu
• Browser (if applicable) [e.g. Chrome, Safari]
• Docker image: e.g. skrashevich/double-take:latest

Additional context
Add any other context about the problem here.

[sirhideo]

doubletake_log.txt

log attached.

[sirhideo]

What i see is that the random_file_name.jpg doesn't even exist in /opt/doubletake/storage/matches, in docker view /.storage, so nothing to be copied across directory.

[skrashevich]

#159 (comment)

[sirhideo]

i have taken a very close look on the logs for every process image. The copy jpg issue only happens occasionally and so some images show up on Match UI and some were totally ignored because i don't see compreface process after fail copy.

I have .storage/latest, .storage/matches and .storage/train directory and mode is 755 (both inside/outside docker). I have now changed to 777 and see how it goes.

[sirhideo]

@skrashevich ok 777 for every directory inside .storage doesn't work either... exactly same error i have attached earlier.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions]

This issue was closed because it has been stalled for 5 days with no activity.