Nothing happens about docker-amd HOT 12 CLOSED

Looks like your not using the latest code/cleint, make sure you update your docker image, your version should be 2.0.10 for the dl client.

from docker-amd.

At the time (29/12) this was the latest version of the docker image. I use watchtower to update the images. I see it grabbed a laters version 3 hours ago. I wil check if that works. The previous version did work on Mac with Docker.

from docker-amd.

Could also be that your ARL token expired. I'm not aware of anyway to check/test that....

from docker-amd.

The normal command line version works with this ARL. But let me see if this newer version of the image works. It sometimes takes a while before it kicks off the actual deemix command.

from docker-amd.

Same thing with the newest version.

INFO:deemix:Linux-4.4.59+-x86_64-with - Python 3.8.5, deemix 2.0.10
INFO:deemix:Generating queue item for: https://deezer.com/album/185143072

from docker-amd.

Sounds like your having an issue with the DL client. You should report it there. Everything is working from my test setup. So its either something particular to your configuration that is causing it. If I cannot reproduce it, then it cannot be investigated....

from docker-amd.

I understand. This same config works on macOS. This problem is on Synology Docker.

from docker-amd.

Sorry, not much I can do to help then.

from docker-amd.

Apparently not. I don't think the other people will be able to help me either since they will say that their software works when you use it from the command line. Thanks for the script and container. I will have to see how I can fix it myself.

from docker-amd.

Same here, built the dockerimage myself.
@mboerma did you manage to fix it?

from docker-amd.

@RaymondSchnyder Nope.

from docker-amd.

https://git.rip/RemixDev/deemix/-/issues This seems to be the upstream project

EDIT: I think i found the problem. Somehow the container sets a weird DNS in /etc/resolv.conf
Changing it to the host dns settings works.

This seems not like an upstream issue.

Anyway, while i look into this, a simple workaround would be to read-only mount the /etc/resolv.conf into your container.

A "fix" would be to set a timeout in the upstream deemix project, so that it doesnt seem like its doing nothing. Also where is this weird DNS coming from? Its not from my docker host...

from docker-amd.