Can't clone the repo - Githubissues

GMP69 commented 3 years ago

Hello, I can't even clone the repo on this. Is Ubuntu Studio 18.04 not supported? (I have the latest version of Docker installed, and Jack running.)

ajboni commented 3 years ago

Hello, what do you mean you cant clone the repo? do you have git installed?

git clone git@github.com:ajboni/mod-docker.git or git clone https://github.com/ajboni/mod-docker.git

GMP69 commented 3 years ago

Thanks, that second option worked - the first one wouldn't play ball for some reason. I thought it was all going smoothly until the end, where I get:

Successfully built ebd6cfdc476a Successfully tagged mod-ui:latest ./run.sh: line 10: docker-compose: command not found

EDIT: I've found I needed to install docker-compose seperately from Docker...so what do I do now? Go through all that downloading again??

ajboni commented 3 years ago

Thanks I will update docs to include docker-compose installation. Now you should be able to run the containers and reach the web interface

chmod +x run.sh
./run.sh
go to http://localhost:8888 and start playing!

GMP69 commented 3 years ago

Unfortunately it's still not playing :( I get this:

Starting mod-ui ... done Attaching to mod-ui mod-ui | useradd: user 'root' already exists mod-ui | Forking... child PID: 14 mod-ui | Cannot connect to server socket err = No such file or directory mod-ui | Cannot connect to server request channel mod-ui | jack server is not running or cannot be started mod-ui | JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock mod-ui | JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock mod-ui | DEBUG:root:[host] popped from queue: transport 0 4.000000 120.000000 mod-ui | Cannot connect to server socket err = No such file or directory mod-ui | Cannot connect to server request channel mod-ui | jack server is not running or cannot be started mod-ui | JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock mod-ui | JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock mod-ui | DEBUG:root:[host] idle? -> 0 mod-ui | WARNING:tornado.general:Connect error on fd 10: ECONNREFUSED mod-ui | WARNING:tornado.general:Connect error on fd 9: ECONNREFUSED mod-ui | DEBUG:root:[host] popped from queue: feature_enable processing 0 mod-ui | DEBUG:root:hmi set midi beat clock OFF mod-ui | Can't create a device key: module 'time' has no attribute 'clock' mod-ui | WARN: Missing file /mod/mod-ui/data/mod_api_key.pub with the public API KEY mod-ui | ERROR: Failed to open HMI serial port, error was: mod-ui | init() got an unexpected keyword argument 'writeTimeout' mod-ui | Using FakeHMI => <mod.development.FakeHMI object at 0x7f3a124d5790> mod-ui | cc start socket missing mod-ui | last state file does not exist or is corrupt mod-ui | last state file does not exist or is corrupt mod-ui | HMI initialized waiting 1 mod-ui | Readsock none mod-ui | Writesock none mod-ui | Host failed to initialize, is the backend running? mod-ui | jack client deactivated NOT mod-ui | jack client deactivated NOT mod-ui exited with code 1

Jack is definitely running.

ajboni commented 3 years ago

I think you are running docker as root. It wont work, you need to run it with the same user that is running JACK

check this: https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user

GMP69 commented 3 years ago

Thanks, I added my user to the Docker group and now get:

Attaching to mod-ui mod-ui | Cannot connect to server socket err = No such file or directory mod-ui | Cannot connect to server request channel mod-ui | jack server is not running or cannot be started mod-ui | JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock mod-ui | JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock mod-ui | Forking... child PID: 28 mod-ui | DEBUG:root:[host] popped from queue: transport 0 4.000000 120.000000 mod-ui | Cannot connect to server socket err = No such file or directory mod-ui | Cannot connect to server request channel mod-ui | jack server is not running or cannot be started mod-ui | JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock mod-ui | JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock mod-ui | DEBUG:root:[host] idle? -> 0 mod-ui | WARNING:tornado.general:Connect error on fd 10: ECONNREFUSED mod-ui | WARNING:tornado.general:Connect error on fd 9: ECONNREFUSED mod-ui | DEBUG:root:[host] popped from queue: feature_enable processing 0 mod-ui | DEBUG:root:hmi set midi beat clock OFF mod-ui | Can't create a device key: module 'time' has no attribute 'clock' mod-ui | WARN: Missing file /mod/mod-ui/data/mod_api_key.pub with the public API KEY mod-ui | ERROR: Failed to open HMI serial port, error was: mod-ui | init() got an unexpected keyword argument 'writeTimeout' mod-ui | Using FakeHMI => <mod.development.FakeHMI object at 0x7fb177043700> mod-ui | cc start socket missing mod-ui | last state file does not exist or is corrupt mod-ui | last state file does not exist or is corrupt mod-ui | HMI initialized waiting 1 mod-ui | Readsock none mod-ui | Writesock none mod-ui | Host failed to initialize, is the backend running? mod-ui | jack client deactivated NOT mod-ui | jack client deactivated NOT mod-ui exited with code 1

Nothing to do with having Alsa and PulseAudio bridged to Jack is it? Should I turn them off? (EDIT: Tried it, no difference!) This seems similar to the issue Naclander reported.

ajboni commented 3 years ago

Indeed it looks very similar to #3 The problem is that the container is not reaching host JACK for some reason

Things to check (you probably already checked most off the list):

Have permission to run docker with your user,
Have permission to run docker-compose with your user.
Do not run the script as root or with sudo.
Check that the container is mounting /dev/shm
Check that JACK is using /dev/shm
Check that JACK is running, user in audio group, rtprio/memlock capabilities. etc.

I cannot reproduce on my end unfortunately, the only way I get the same error is turning off jack or running the script as sudo.

ajboni commented 3 years ago

Maybe the container was created with root and needs to be recreated.

Can you try removing images and recreating them?

docker image rm -f mod-host mod-ui ./run.sh

GMP69 commented 3 years ago

I tried removing and recreating them and it ends with this:

Recreating mod-ui ... error

ERROR: for mod-ui no such image: sha256:ebd6cfdc476a5a02403ecf603979fe5ae9b9047e0237d1fffd11178a83b6b38c: No such image: sha256:ebd6cfdc476a5a02403ecf603979fe5ae9b9047e0237d1fffd11178a83b6b38c

ERROR: for mod-ui no such image: sha256:ebd6cfdc476a5a02403ecf603979fe5ae9b9047e0237d1fffd11178a83b6b38c: No such image: sha256:ebd6cfdc476a5a02403ecf603979fe5ae9b9047e0237d1fffd11178a83b6b38c ERROR: The image for the service you're trying to recreate has been removed. If you continue, volume data could be lost. Consider backing up your data before continuing.

Continue with the new image? [yN]y Recreating d1adbded66e3_mod-ui ... done Attaching to mod-ui mod-ui | Forking... child PID: 28 mod-ui | Cannot read socket fd = 3 err = Success mod-ui | CheckRes error mod-ui | Could not read result type = 22 mod-ui | Client name = mod-host conflits with another running client mod-ui | Cannot connect to the server mod-ui | JackShmReadWritePtr1::~JackShmReadWritePtr1 - Init not done for -1, skipping unlock mod-ui | JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock mod-ui | JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock mod-ui | DEBUG:root:[host] popped from queue: transport 0 4.000000 120.000000 mod-ui | Cannot read socket fd = 9 err = No such file or directory mod-ui | CheckRes error mod-ui | Could not read result type = 22 mod-ui | Client name = mod-ui conflits with another running client mod-ui | Cannot connect to the server mod-ui | JackShmReadWritePtr1::~JackShmReadWritePtr1 - Init not done for -1, skipping unlock mod-ui | JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock mod-ui | JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock mod-ui | DEBUG:root:[host] idle? -> 0 mod-ui | WARNING:tornado.general:Connect error on fd 10: ECONNREFUSED mod-ui | WARNING:tornado.general:Connect error on fd 9: ECONNREFUSED mod-ui | DEBUG:root:[host] popped from queue: feature_enable processing 0 mod-ui | DEBUG:root:hmi set midi beat clock OFF mod-ui | Can't create a device key: module 'time' has no attribute 'clock' mod-ui | WARN: Missing file /mod/mod-ui/data/mod_api_key.pub with the public API KEY mod-ui | ERROR: Failed to open HMI serial port, error was: mod-ui | init() got an unexpected keyword argument 'writeTimeout' mod-ui | Using FakeHMI => <mod.development.FakeHMI object at 0x7f27f61c5700> mod-ui | cc start socket missing mod-ui | last state file does not exist or is corrupt mod-ui | last state file does not exist or is corrupt mod-ui | HMI initialized waiting 1 mod-ui | Readsock none mod-ui | Writesock none mod-ui | Host failed to initialize, is the backend running? mod-ui | jack client deactivated NOT mod-ui | jack client deactivated NOT mod-ui exited with code 1

Do those first few lines shed any light? I don't know how to check this /dev/shm stuff you mention, or JACK's rtprio/memlock capabilities. I'm in way over my head already! Which versions of Linux & Jack did you get this to work on?

GMP69 commented 3 years ago

JACK seems to be using /dev/shm:

ls -lah /dev/shm total 103M drwxrwxrwt 3 root root 260 May 5 14:34 . drwxr-xr-x 19 root root 4.6K May 5 14:27 .. -rw-rw-r-- 1 gav gav 103M May 5 14:28 jack-1000-0 -rw-rw-r-- 1 gav gav 1.2K May 5 14:28 jack-1000-1 drwxrwx--- 2 gav gav 120 May 5 14:28 jack_db srwxrwxr-x 1 gav gav 0 May 5 14:28 jack_default_1000_0 -rwxrwxr-x 1 gav gav 12 May 5 14:28 jack_sem.1000_default_a2j -rwxrwxr-x 1 gav gav 12 May 5 14:28 jack_sem.1000_default_dbusapi -rwxrwxr-x 1 gav gav 12 May 5 14:28 jack_sem.1000_default_freewheel -rwxrwxr-x 1 gav gav 12 May 5 14:28 'jack_sem.1000_default_PulseAudio JACK Sink' -rwxrwxr-x 1 gav gav 12 May 5 14:28 'jack_sem.1000_default_PulseAudio JACK Source' -rwxrwxr-x 1 gav gav 12 May 5 14:28 jack_sem.1000_default_system -rw-rw-rw- 1 gav gav 70K May 5 14:28 jack-shm-registry

ajboni commented 3 years ago

Well , now it seems you hit the exact problem as #3 . From the log I understand the container reach JACK mod-ui | Client name = mod-host conflits with another running client

I'm running latest linux mint with kxstudios repos. Jack is being launched via cadence. I also did some tweakings in the past 3 years and I unfortunately don't know what exact settings I've changed.

I suppose it might be a OS or JACK config that we need to be able to run it. Unfortunately I don't really know what/how to find it! I think in qjackctl there are more options, maybe try some settings there? (realtime, memory lock or something)

Sorry I cannot be more helpful...

GMP69 commented 3 years ago

Oh well, thanks anyway - it would be nice to play with that Pedalboard but ultimately I do have all the plugins available on Carla anyway, so I ought to just play with that. ...or maybe I'll try getting MODEP running in a virtual machine on Linux. Might be more straightforward than this Docker stuff after all!

ajboni / mod-docker

Can't clone the repo #4