motioneye-project/motioneye

error " docker: failed to register -sh: 15: layer" during installation of motioneye in docker on usb drive

Open

#2,303 opened on Mar 2, 2022

View on GitHub
 (19 comments) (0 reactions) (0 assignees)Python (3,533 stars) (636 forks)batch import
help wantedtroubleshooting

Description

below the command I gave and the result....

docker is on usb drive connected to raspberry 4b. Who can help?

$ sudo docker run --name="motioneye" -p 8765:8765 -p8081:8081 --hostname="motioneye" -v /et c/localtime:/etc/localtime:ro -v /etc/motioneye:/etc/motioneye -v /var/lib/motioneye:/var/l ib/motioneye --restart="always" --detach=true --device=/dev/video0 ccri$ san/motioneye:mast er-armhf Unable to find image 'ccrisan/motioneye:master-armhf' locally -sh: 13: $: not found $ -sh: 14: Unable: not found $ master-armhf: Pulling from ccrisan/motioneye eaaa43e22ddc: Extracting 45.71MB/45.71MB 38b5f9df17bb: Download complete 5a36f2cd0f41: Download complete 957aa23b13ac: Download complete 1b23938bf6aa: Download complete docker: failed to register -sh: 15: layer: symlink ../285ba1cb3339ec05fde94f4c05bf2701349em aster-armhf:: not found21bf6e905ae6568963d7a2ce919e/diff /srv/d ev-disk-by-uuid-15DF-36CB/docker/overlay2/l/7U57GJT2U2YWP3U6RC4WF6D2D2: no such file or dir ectory.

Contributor guide

Tech stack
dockershell
Domain
devops
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Docker knowledgeLinux filesystemRaspberry Pi
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
The error occurs due to Docker overlay2 layer symlink failure, likely because the USB drive is formatted with a filesystem that does not support symlinks (e.g., FAT32) or due to incorrect mount permissions. Check the filesystem type and remount with appropriate options. Review the Docker storage driver configuration and consider using a different driver or moving the Docker data directory to a filesystem that supports symlinks, such as ext4. The issue comments may contain additional troubleshooting steps.