grundic / jamulus-docker Goto Github PK

I get a "bad address" status when I try to include the --centralserver flag when I run the container. I'm wondering if anyone has had success doing this or if the bad address is coming from inside the container as the Docker internal address? Any clues?

Should we assume most or all supported command-line parameters as per https://github.com/corrados/jamulus/wiki/Command-Line-Options are supported in latest docker build (v3.5.11)? Wiki needs an update to include --mutestream, --norecord, --multithreading, etc and deprecate --history.

https://github.com/grundic/jamulus-docker#parameters

Jamulus 3.9.0 has been released a few days ago:
https://github.com/jamulussoftware/jamulus/releases

Would it be possible to update this docker container to the current version?

Is it possible to update the docker image to the new release 3.8.2?

Hi, I have a question. I can see that you updated the image to 3.8.1 on Oct 31st. It is not available on docker registry yet. Does it need some action or just patience?

Thanks,

Rob Meerwijk

Would it be possible to migrate the docker image to Jamulus 3.7.0?
I've tried to create a pull requests, but unfortunately I could not create a new branch for the change.

Hi,
I have set up a public subnet in AWS Fargate ECS (on linux platform) to run this docker. Jamulus seems to be starting ok according to the AWS log, but I cannot connect from the Jamulus client.

Looking into this, in AWS the task is assigned:
Public IP
16.171.60.195
Private IP
10.0.7.124

The Jamulus log states:
2022-10-07 08:54:13 | Using "10.0.7.124" as external IP.
2022-10-07 08:54:13 | - Starting in server mode by default (due to compile time option)
2022-10-07 08:54:13 | No GUI support compiled. Running in headless mode.

Using the local IP as external seems like a source for the problem. Any thoughts on how to get it all running?

Any chance the docker image could be updated at same time as the main release?

Hi! I am quite new to docker and also Jamulus. I would like to setup a Jamulus docker on my NAS so I can run an Jamulus server on this NAS.

Here is what I did so far:

On my Synology NAS I installed the Docker 'application' that can manage docker containers on the NAS. I followed a tutorial to install a Handbrake container on my NAs to get a feel of how it works. That went great.

So next I downloaded the image for the Jamulus docker and created a container on the NAS. I does look like this worked and the container is running. But I don't know what to do next. Is suppose I need to start the Jamulus server within the container. I do see a terminal windows in the details of the container, but I don't know how to use that...

Is there a way I set up the container to also start the jamulus server with some specific parameters when the container is launched? I can set 'Environment' variables in the docker container but I am not sure if I can add a start server command here?

I hope someone can point me in the right direction. Because I am using the NAS docker application it might work a bit different then when I am on a 'normal' server with access to the commandline.

As far as I understood, it is just one configuration file which would be added, right? The text in your readme file could be put in the Jamulus Wiki on Github. What do you think?

Hi, great job on the packaging - thanks!

Problem I've found is that jamulus segfaults immediately on launch if -d is specified to detach the terminal, as per your example docker command. If I omit -d, it runs fine, but it outputs to the terminal.

Any experience on running this container on azure container instances?
The Deployment failed on creating or updating the container group twice and self repaied later.
The container is up an running, but the instance remains in failed state.
I have the impression i can connct with jamulus client