Stream to Playback Devices with Different Capabilities

[simoncn]

See this post for instructions on how to do this installation.

[chip]

(19-06-2019 07:52)simoncn Wrote:  See this post for instructions on how to do this installation.

OK, I think I understand the instructions.

Is it possible to run more than one Container with MinimServer?
I am thinking of possibly having MinimServer running directly on my NAS and two instances in one container per instance.
Can I just follow the instructions twice?

[chip]

(19-06-2019 07:52)simoncn Wrote:  See this post for instructions on how to do this installation.

Hi Simon,
I apologize if my question seems obvious but I want to be sure to be sure.
I have read thought the QNAP instructions for downloading and installing Container Station and your instructions to install MinimServer in a Container.
I think I understand but I have one questions before beginning my adventure.

In step 10 the instructions say "Start and Open Container Station."
Should I install Container Station from the QNAP Applications Download before beginning this procedure or do I install Container station at this point in the procedure.

I am getting there with your help and thank you for that.
Chip

[simoncn]

It doesn't matter when you download and install Container Station as long as you have done this before the "start and open" step.

You should be able to run multiple containerised instances of MinimServer but I haven't tried this myself.

[chip]

Hi Simon,
I started the Docker creation today and ran into a problem at
9) Run the command: sh ../run/docker.sh build -t minimserver:0.8.5.2

I am running the commands using putty

Step 5 seems successful
[~] # cd /share/Public/Docker/build
[/share/Public/Docker/build] #

When I copy the command from step 9 and press enter
[/share/Public/Docker/build] # sh ../run/docker.sh build -t minimserver:0.8.5.2
"docker build" requires exactly 1 argument.
See 'docker build --help'.

Usage: docker build [OPTIONS] PATH | URL | -

Build an image from a Dockerfile
[/share/Public/Docker/build] #

10) Start Container Station > OK
11) Under Images you should see ... > nothing is listed
I do not think step 9) completed since I cannot see an image in Container Station.

What did I miss?
Any ideas?
I seem to be stuck at this point.

Chip

[simoncn]

Please check step 9 again. It looks like you did not include the period (.) at the end of the line.

[chip]

Hi Simon,
The period was missing as you pointed out.
I ran the command again with the last period and I have the image.

I have a couple of other points I would like to ask you based on your instructions.

13) On the Advanced Settings page, select Network and change the network mode to Host (ignoring the warning message)
The error message:
The port may conflict with the NAS port when selecting Host mode.
Use local host network (command: --net=host)
Note: This option allows containers to have full access to the host network interface.
This is the message I should ignore.

14) On the Advanced Settings page, select Shared Folders and create a mapping for your MinimServer library folder to a mount point in the Docker container (for example, /Music)
When I select shared folders I have three options.
a) New Volume
b) Volume from host
c) Volume from container
I used Volume from host to create the mount point.
Is this correct?

The container seems to be running and I can see the library when I select this server using Linn Kazoo. I was surprised when I checked Kazoo for this server and saw the library fully populated. I thought I would have to run a scan.
Does setting up the container automatically run the scan?

I am getting there thanks to you help.
Chip

[simoncn]

For 13), yes, this is the warning message you should ignore.

For 14), you need Volume from host. This is the "real" folder on your NAS that you are mapping to a "virtual" folder in your container.

[chip]

(23-06-2019 07:49)simoncn Wrote:  For 13), yes, this is the warning message you should ignore.
For 14), you need Volume from host. This is the "real" folder on your NAS that you are mapping to a "virtual" folder in your container.

Hi Simon,
I have my container running now.
Thanks for your patience and assistance,
Chip