Only listens to ipv6 interface about multistreamer

[k1ck3r]

check the config /etc/multistreamer/config.yaml within the docker. don't have much experience with the docker, but you also should check the nginx config as well. my current config is as follow:

https://gyazo.com/99be93df7cb6798b8984b6557cea4f7c

[Llorx]

Yes, I've modified the multistreamer/config.yml.tmpl inside the rootfs (as I don't have access to the docker containers contents) and modified the http_listen to http_listen: '8081 ipv6only=off', but nothing happens.

[k1ck3r]

file should be multistreamer/config.yml not multistreamer/config.yml.tmpl

also remove any other options like ipv6only=off if you want to be sure that every part of the config is properly filled

[Llorx]

The tmpl file is just a file that already exists with variables and such, so I thought that was processed at some point replacing the variables with config values.

Will try without tmpl.

[jprjr]

Question: have you tried connecting to an IPv4 address anyway? What happens if you do?

An IPv6 wildcard should be able to accept IPv4 connections as well.

What OS are you running on?

[Llorx]

Centos.

I would like to know if modifying the provided tmpl file I am doing something. I modified it to add the ipv6only thingy and also modified it to this:

http_listen: '0.0.0.0:8081'

Rebuilt the docker containers but still listens to the ipv6 interface.

I remark than I'm modifying the multistreamer/config.yml.tmpl inside rootfs, and I'm not sure if is the way of doing this.

[jprjr]

I'd need a few more details, like what version of CentOS. If you can provide what version of Docker you're using, that'd be great too.

Additionally, see my other question - have you tried connecting via IPv4 anyway, what kind of response do you get?

[Llorx]

Oh, I thought that you said if I forced it to listen to a IPv4 interface.

Yes, I started to debug because connecting via IPv4 throws me connection refused, so the first thing to do is to check for open ports.

I'm using CentOS 7 and Docker version 1.13.1.

The question I want to know is: Do modifying the multistreamer/config.yml.tmpl file will overwrite the multistreamer/config.yml one? Because I think that the http_listen: '0.0.0.0:8081' don't works. It has to listen for IPv4 when you configure Nginx like that so I guess that the config is not reaching the container multistreamer/config.yml file.

[jprjr]

Modifying the config.yml.tmpl file should do what you want - how are you building the image and launching the container? Are you sure you're actually running the newly-built image?

[Llorx]

I'm new to docker so I'm not 100% sure, but searching around Internet I tried with this:

docker-compose rm // To remove
docker-compose up --build

[jprjr]

So the docker-compose file over in jprjr/docker-multistreamer doesn't specify a build parameter, just image. So using docker-compose to build won't actually build it.

The docker-compose file is in the old version 1 format, which doesn't let you specify an image tag and build instruction in the same service. If I update to version 2, users will have to update their override files to work with the new format.

so, to build the image, you'll want to run something like:

docker build -t jprjr/multistreamer:12.0.0-1 .
docker-compose up

Make sure that tag is what's in the docker-compose.yml file.

[jprjr]

I've been considering discontinuing this project for some time now. I'm sorry I couldn't solve your issue, but I just don't enjoy working on multistreamer anymore.