-
Notifications
You must be signed in to change notification settings - Fork 281
help installing ARM #1042
Replies: 1 comment · 4 replies
-
What does "docker logs automatic-ripping-machine" output |
Beta Was this translation helpful? Give feedback.
All reactions
-
That shows: However, docker logs arm-rippers shows a lot. Here's the last bit of it: *** Killing all processes... *** Killing all processes... *** Killing all processes... *** Killing all processes... *** Killing all processes... *** Killing all processes... *** Killing all processes... *** Killing all processes... *** Killing all processes... |
Beta Was this translation helpful? Give feedback.
All reactions
-
That is an issue a few users have encountered, its being worked on at the moment to resolve. A work around is to remove the music folder in /home/arm, or if it is a symbolic link then remove the link |
Beta Was this translation helpful? Give feedback.
All reactions
-
The music directory never gets created. The docker startup file tells it that the directory is located in the /home/arm directory The contents of the /home/arm directory are as follows: drwxr-xr-x 3 arm arm 4096 Jan 20 12:34 ./ |
Beta Was this translation helpful? Give feedback.
All reactions
-
Ok |
Beta Was this translation helpful? Give feedback.
-
Running linux server 20.04
I have attempted to installed ARM using the documentation found here:
https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/docker
I had difficulties understanding what to replace int he start_arm_container.sh file, but I managed to change what I could figure out. Here's the contents of what I have:
#!/bin/bash
docker run -d
-p "8181:8181"
-e ARM_UID="1006"
-e ARM_GID="1006"
-v "/home/arm"
-v "/home/arm/music"
-v "/home/arm/logs"
-v "/home/arm/media"
-v "/etc/arm/config"
--device="/dev/sr0:/dev/sr0"
--device="/dev/sr1:/dev/sr1"
--device="/dev/sr2:/dev/sr2"
--device="/dev/sr3:/dev/sr3"
--privileged
--restart "always"
--name "arm-rippers"
--cpuset-cpus='4'
automaticrippingmachine/automatic-ripping-machine:latest
I changed the port number as 8080 was being used by something else
I added the UID and GID that corresponded to the arm user
I didn't change the volume mounts as I'm just trying to get it running for now. The place where I want my videos and music to be eventually will be in a different location.
I didn't change the --device settings as I wasn't quite sure what I was looking for.
I changed the cpuset-cups to 4 as I'm not sure what I want it to look like yet
Outupt of lsscsi -g for my DVD drive entry only:
[6:0:0:0] cd/dvd TSSTcorp CDDVDW SE-218CB MF00 /dev/sr0 /dev/sg5
After editing these things, when I run
sudo nano start_arm_container.sh
I get
'7121ec761dc331e9bf66aaf2156ad04a79af800d7416bedb33fd333bfb246892'
I try going to the IP address for the server with the port number I designated and I get nothing.
I have very little experience with docker and I'm not sure what to do to troubleshoot
Thank you for any help
Jason
Beta Was this translation helpful? Give feedback.
All reactions