Closed dannydanchev closed 1 year ago
Hi sorry to hear you've had some issues.
Only time I managed to get a different output was when following the docker-compose.yml file in the master branch and I added a
/app
directory for midarr in but then got this outputError response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/app/entry.sh": stat /app/entry.sh: no such file or directory: unknown
^This is similar to the error logged by my Raspberry Pi before we added arm64
support. Our release build supports architectures amd64
and arm64
which I would have thought your machine falls under amd64
Could you try running Midarr on a more recent machine and see if that works?
I ran a fresh README docker compose on an Intel i7 ubuntu server without any issue.
Oh never mind, I misread the errors. It looks like Midarr does successfully build, but crashes when looking for the entry point script.
I tried forking the repo and running the docker-compose.yml and that one does start successfuly.
I believe I might be experiencing some sort of permission issue? For example recyclarr in the same /srv/recyclarr/... directory starts, but when I try to create a config file it fails to do so. I had to run sudo chown -R 1000:1000 /srv/recyclarr/appdata
and that fixed the issue.
However trying the same with midarr doesn't seem to help.
I am using hotio's docker images and he seems to have PUID and PGID under the environment tab in his compose files. Trying to add them in midarr doesn't help thoe.
I was able to replicate the issue. Midarr will crash if either your Radarr or Sonarr is unreachable. Please make sure their config are both set and correct.
Can you give this a try? Just put in your Radarr and Sonarr details:
version: "3.4"
volumes:
postgresql-data:
services:
midarr:
container_name: midarr
image: ghcr.io/midarrlabs/midarr-server:latest
ports:
- 4000:4000
environment:
- APP_URL=http://midarr:4000
- DB_USERNAME=my_user
- DB_PASSWORD=my_password
- DB_DATABASE=my_database
- DB_HOSTNAME=postgresql
- SETUP_ADMIN_EMAIL=admin@email.com
- SETUP_ADMIN_NAME=admin
- SETUP_ADMIN_PASSWORD=somepassword
- RADARR_BASE_URL=radarr:7878 # required
- RADARR_API_KEY=someApiKey # required
- SONARR_BASE_URL=sonarr:8989 # required
- SONARR_API_KEY=someApiKey # required
depends_on:
postgresql:
condition: service_healthy
postgresql:
container_name: postgresql
image: postgres
volumes:
- postgresql-data:/var/lib/postgresql/data
environment:
- POSTGRES_USER=my_user
- POSTGRES_PASSWORD=my_password
- POSTGRES_DB=my_database
healthcheck:
test: "exit 0"
Success!!
Using the provied docker-compose.yml I was able to start the container and launch the web interface. Only had to add my media library and I am watching.
Would it be possible to have the postgresql-data volume follow my current mappings and be stored in /srv/midarr/data
?
And how would I integrate my docker-network
in the compose file?
Would it be possible to have the postgresql-data volume follow my current mappings and be stored in
/srv/midarr/data
? And how would I integrate mydocker-network
in the compose file?I was able to achieve this by using the following docker-compose.yml edited to better fit the others I have.
version: "3.7"
services:
midarr:
container_name: midarr
image: ghcr.io/midarrlabs/midarr-server:latest
ports:
- "4000:4000"
environment:
- APP_URL=http://midarr:4000
- DB_USERNAME=my_user
- DB_PASSWORD=my_password
- DB_DATABASE=my_database
- DB_HOSTNAME=postgresql
- SETUP_ADMIN_EMAIL=admin@email.com
- SETUP_ADMIN_NAME=admin
- SETUP_ADMIN_PASSWORD=somepassword
- RADARR_BASE_URL=radarr:7878
- RADARR_API_KEY=d90f102c62b44fd8adf37f5a9870f123
- SONARR_BASE_URL=sonarr:8989
- SONARR_API_KEY=270f828df52441e8b209a7a1118c0123
volumes:
- /home/danny/storage/media/library:/media/library
networks:
- docker-network
depends_on:
postgresql:
condition: service_healthy
postgresql:
container_name: postgresql
image: postgres
environment:
- POSTGRES_USER=my_user
- POSTGRES_PASSWORD=my_password
- POSTGRES_DB=my_database
volumes:
- /srv/midarr/appdata:/var/lib/postgresql/data
networks:
- docker-network
healthcheck:
test: "exit 0"
networks:
docker-network:
external: true
After running docker system prune -a
and then recreating the container from scratch everything works as expected :) (love the UI so far <3)
After taking a more in depth look at the error logs I was experiencing previously and then taking into account the compose file you provided (mentioning that both radarr and sonarr data is required) I can confidently say that this was user error on my part. I only included the radarr API key and deleted the parts mentioning sonarr.
Thank you for helping me resolve an issue caused by me not properly reading and configuring a simple docker compose file facepalm
Ah good to hear you were able to resolve this. Thank you for posting detailed info and for your feedback.
https://github.com/orgs/midarrlabs/projects/1/views/1?filterQuery=fail
I think this could have been easier to resolve if the error logs were more detailed as to what was failing, so I've added a couple tickets to account. Hopefully be in the next release π
Please feel free to reach out anytime with issues or feature ideas! I'm more than happy to help πββοΈ
Hey I am in the process of setting up my very first home media server on an old Athlon X2 machine. I've successfuly managed to get the *arr stack running with hardlinks set up as per the TRaSH guides and needed a simple and lightweight way to stream my media files. So far midarr-server seems to be exactly what I am looking for but I am facing some issues regarding the docker compose setup.
I keep my docker-compose.yml files each in a seperate directory under
/srv/<service-name>
and then each container data resides in/srv/<service-name>/appdata
. To "connect" them together I have created a docker network calleddocker-network
.Following the docker compose example in the README I created a new
database-data
volume but after runningdocker compose up
I got the following error:All dependencies are up to date
psql: error: connection to server on socket "/run/postgresql/.s.PGSQL.5432" failed: No such file or directory
Crash dump is being written to: erl_crash.dump...
midarr exited with code 1
I also tried keeping the database under
/srv/midarr/data
but got the same error. My docker-compose.yml is attached bellow:Only time I managed to get a different output was when following the docker-compose.yml file in the master branch and I added a
/app
directory for midarr in but then got this outputError response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/app/entry.sh": stat /app/entry.sh: no such file or directory: unknown
I am quite new to managing containers with docker compose and would really appreciate some feedback on what I might be doing wrong.
Running Debian 12 with Docker version 24.0.5.
My Radarr docker-compose.yml file