Having issue trying to install a docker. 

Unraid: Version: 6.9.0-beta22

 

 

Quote

 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='motioneye' --net='bridge' -e TZ="America/Denver" -e HOST_OS="Unraid" -e 'UID'='1000' -e 'GID'='100' -p '8765:8765/tcp' -v '/mnt/user/videos/camera':'/var/lib/motioneye':'rw' -v '/mnt/user/appdata/motioneye':'/etc/motioneye':'rw' 'djaydev/motioneye' 

045b44ed514a302672aa7c0e92dcfa38155a42be66c4244bd2dc4eb56663f086
/usr/bin/docker: Error response from daemon: error while creating mount source path '/mnt/user/appdata/motioneye': mkdir /mnt/user/appdata/motioneye: read-only file system.

The command failed.

 

 

this happens with or without using cache for appdata shared folder

 

Please post the diagnostics: Tools -> Diagnostics

mserver-diagnostics-20200702-1338.zip

 

diagnostics attached

 

i have tried some permission commands such as

 

chown -R nobody:users /mnt/user/appdata

chmod -R 777 /mnt/user/appdata

 

and

 

newperms /mnt/user/appdata

 

neither solved it, but i did not reboot since.

so i will reboot, i have tried two different motioneye dockers but not any other dockers

 

to provide a short follow up.

 

1: i updated unraid

2: assigned two new pool devices thinking i could have motion eye use the one pool because it doent need to be protected by parity.

3. messed around with network settings trying to assign a ethernet port to motion eye. That messed up my internet connection on unraid.

4. restored usb from backup from just before the unraid update to a different usb drive

5. figured out i have to use the same usb drive

6. restored from backup to original usb drive

7. unraid works again

8. updated unraid

9. assigned the new pool devices again

 

somewhere in there i removed motion eye because it was not starting and have not been able to set it back up since

Edited July 2, 20206 yr by Mezhom

did a restart, tried the other motioneye docker

 

Quote

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='MotionEye' --net='bridge' -e TZ="America/Denver" -e HOST_OS="Unraid" -e 'PUID'='99' -e 'PGID'='100' -p '8765:8765/tcp' -v '/mnt/cache/appdata/MotionEye/config':'/etc/motioneye':'rw' -v '/mnt/user/RP/':'/var/lib/motioneye':'rw' 'malvarez00/docker-motioneye' 

63704aeef3f3b11a07a6c61bc620033084ccb3f1b7aa6258dc2175887bc7ce77
/usr/bin/docker: Error response from daemon: error while creating mount source path '/mnt/cache/appdata/MotionEye/config': mkdir /mnt/cache/appdata/MotionEye: read-only file system.

The command failed.

 

did it with the original docker i use

 

Quote

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='motioneye' --net='bridge' -e TZ="America/Denver" -e HOST_OS="Unraid" -e 'UID'='1000' -e 'GID'='100' -p '8765:8765/tcp' -v '/mnt/user/RP/':'/var/lib/motioneye':'rw' -v '/mnt/cache/appdata/motioneye':'/etc/motioneye':'rw' 'djaydev/motioneye' 

79e179aaf053e1701b29045731a69a916298365faa54ca554d6b468f1304e081

The command finished successfully!

but wont start

 

1. So i erased any files in the appdata/motioneye user and cache locations. i seem to have permission after the restart.

2. Re installed the docker

 

Quote

Pulling image: djaydev/motioneye:latest

IMAGE ID [695145111]: Pulling from djaydev/motioneye. 
IMAGE ID [cbdbe7a5bc2a]: Pulling fs layer. Downloading 100% of 3 MB. Download complete. Extracting. Pull complete. 
IMAGE ID [038ae5e57f01]: Pulling fs layer. Downloading 100% of 64 MB. Verifying Checksum. Download complete. Extracting. Pull complete. 
IMAGE ID [43191dbcbbc1]: Pulling fs layer. Downloading 100% of 625 B. Verifying Checksum. Download complete. Extracting. Pull complete. 
IMAGE ID [9fca2430be1e]: Pulling fs layer. Downloading 100% of 625 B. Verifying Checksum. Download complete. Extracting. Pull complete. 
Status: Downloaded newer image for djaydev/motioneye:latest

TOTAL DATA PULLED: 67 MB

 

Command:root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='motioneye' --net='bridge' -e TZ="America/Denver" -e HOST_OS="Unraid" -e 'UID'='1000' -e 'GID'='100' -p '8765:8765/tcp' -v '/mnt/user/RP/':'/var/lib/motioneye':'rw' -v '/mnt/user/appdata/motioneye/':'/etc/motioneye':'rw' 'djaydev/motioneye' 

054a1deec5320a2a525c8c096969dac2e53196b5dbc212146a6c9f1a57b6137f

The command finished successfully!

 

Docker tries to start, shows port mapping: 172.17.0.3:8765 / TCP192.168.1.234:8766

but then stops down immediately

 

 

 

My other dockers seem to be working (Sonarr, Pihole, Plex, Krusader, calibre)

Radarr seems to be sitting at the dots bouncing back and forth screen

Edited July 2, 20206 yr by Mezhom

got something figured out.

 

Rolled back to UNRAID 6.8.3

 

motioneye docker works again

 

Sonarr loads up again too

 

6.9 unraid is not quite ready from what i found too many issues for me.

 

i think i would have rather had a more robust unassigned drives to use them for dockers. I had issues trying to run lancache on a unassigned drive. server would become unresponsive 3-4 times a week. 

 

maybe another unraid server is my answer instead of messing up what i got perfected right now.

Edited July 2, 20206 yr by Mezhom

1 hour ago, Mezhom said:

got something figured out.

 

Rolled back to UNRAID 6.8.3

 

motioneye docker works again

 

Sonarr loads up again too

 

6.9 unraid is not quite ready from what i found too many issues for me.

 

i think i would have rather had a more robust unassigned drives to use them for dockers. I had issues trying to run lancache on a unassigned drive. server would become unresponsive 3-4 times a week. 

 

maybe another unraid server is my answer instead of messing up what i got perfected right now.

Did you try 

Tools> Docker Safe New Perms

Good luck

yes i actually did try that, i also noticed that excludes appdata.

 

thats why i did the 

 

chown -R nobody:users /mnt/user/appdata

chmod -R 777 /mnt/user/appdata

 

commands

 

permission seemed to work once i restarted. so not sure which step fixed it as i did all those steps before trying to restart.

but that did not fix the motioneye docker not starting. it would install. just wouldnt run. also my sonarr wouldn't load, radarr would

8 hours ago, Mezhom said:

chown -R nobody:users /mnt/user/appdata

chmod -R 777 /mnt/user/appdata

This could mess up docker containers that do not want those permissions.   It is normally recommended to leave the permissions on appdata alone as far as possible, and if you do make changes limit them as much as is practical.

One other thing to note from all this. My Pi-Hole is up and running i can log in and check. but after all this messing around anything using the pihole as a DNS doesn't have internet. 

 

 Project for another day.

 

Not sure which part broke it. But the docker is up and running.