Jump to content

[Support] knex666 - Icecast

Featured Replies

Posted

Application Name: Icecast

Overview: Support for Docker image of Icecast

Application: Icecast - http://icecast.org/

Docker Hub: https://hub.docker.com/r/infiniteproject/icecast/

GitHub: https://github.com/maschhoff/docker/tree/master/icecast

 

Please read all information in the Overview Box. And use the configuration and files providet on github.

Is a good combination with Mopidy

For any question - dont mind to ask!

Edited by knex666

  • Author

reserved

  • 9 months later...

even though im specifying the directive

 

    <security>
        <chroot>0</chroot>
        <changeowner>
            <user>icecast</user>
            <group>icecast</group>
        </changeowner>
    </security>

 

The docker wont start because:

 


Couldn't find user "icecast" in password file
Couldn't find group "icecast" in groups file

 

What do i have to do?

Tells me :

 

Couldn't find user "nobody" in password file
Couldn't find group "nobody" in groups file
ERROR: You should not run icecast2 as root
Use the changeowner directive in the config file

 

I use:

        <changeowner>
            <user>nobody</user>
            <group>nobody</group>
        </changeowner>

 

I check:

 

image.png.515deb1627fc2f70bbecc4a86b47171c.png

 

 

I add variables to container:

 

 

image.thumb.png.e862da55bad24a73e494f33eee6bb9a7.png

Still user/group "Nobody" found.

 

Whats wrong with this container?

 

Edited by je82

I'm a complete newb at docker but it looks like this container is broken as it is not running:

 

RUN addgroup -S icecast && \

adduser -S icecast

 

There's no user icecast for this docker container, so the icecast server won't start because it has no users, anyone have any idea how to fix it?

7 hours ago, knex666 said:

As written in the description please copy and use the icecast.xml from here:

https://github.com/maschhoff/docker/tree/master/icecast

 

This should work fine.

 

Cheers and merry xMas

I used this config file, it gives me the same error.

Config file contains:

 

            <user>icecast</user>
            <group>icecast</group>

This user is not exist within the container according to icecast and it won't boot.

Or is it something else that is wrong and it errors out the wrong thing? Should i be looking at something else?

 

I tried a different container for Icecast and all of them give the exact same error, the user/group does not exist, i've tried with user:group nobody:users as this is the user that runs docker containers on unraid but this doesn't work either.

 

Ideas would be welcome, merry christmas!

Edited by je82

  • 9 months later...

I'm having the same problem with this container. I assume setting 99 and 100 doesn't work because the container has no idea what to do with it. I think I'm just going to go with a VM for this setup.

 

  • 1 year later...

Hi guys,

Docker Icon is not displayed at all :

 

Ice-Cast-Couilles.png

 

Is there any workaround ?

Thanks.

 

  • Author
1 hour ago, PicPoc said:

Hi guys,

Docker Icon is not displayed at all :

 

Ice-Cast-Couilles.png

 

Is there any workaround ?

Thanks.

 

The icon URL is broken, just use an other icon and put the URL inside the container configuration. 

Cheers 

ok. thanks.

Another problem :

I want to user the same IP for Apache-PHP and IceCast.

Same IP, but not the same port.

Apache-PHP 192.0.2.100:80

IceCast : 192.0.2.100:8000

 

It's impossible to set the same IP.

Is there any workaround ?

  • Author
5 hours ago, PicPoc said:

Another problem :

I want to user the same IP for Apache-PHP and IceCast.

Same IP, but not the same port.

Apache-PHP 192.0.2.100:80

IceCast : 192.0.2.100:8000

 

It's impossible to set the same IP.

Is there any workaround ?

Yes, use bridge instead of bro0

Yes I try it but no way :(

  • 1 year later...
On 4/24/2022 at 6:31 AM, knex666 said:

Yes, use bridge instead of bro0

Just to know :

I used "Host" instead "br0", because br0 doesn't work with the same IP of unraid.

Question, is it possible to use both Icecast and Snapcast with the same Mopidy player container? I'd like to have LAN clients on snapcast and broadcast over WAN using Icecast.

  • Author
43 minutes ago, JonathanM said:

Question, is it possible to use both Icecast and Snapcast with the same Mopidy player container? I'd like to have LAN clients on snapcast and broadcast over WAN using Icecast.


I thing that was the way I ran Mopidy usibg that config

 


[iris]
snapcast_enabled = true
snapcast_port = 6680

[stream]
enabled = true
protocols =
    http
    https
    mms
    rtmp
    rtmps
    rtsp
timeout = 5000

  • 2 weeks later...

Hello! attempting to get this up and running - I copied/added the xml and void files as specified, but still am getting the following error when trying to spin up the container: 

 

docker run
  -d
  --name='Icecast'
  --net='bridge'
  -e TZ="America/New_York"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Diskomo"
  -e HOST_CONTAINERNAME="Icecast"
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:8000]/'
  -l net.unraid.docker.icon='https://rockhost.com/wp-content/uploads/2018/11/icecast-server-hosting-cdn.jpg'
  -v '/mnt/user/appdata/icecast/icecast.xml':'/etc/icecast.xml':'rw'
  -v '/mnt/user/appdata/icecast/void.mp3':'/usr/share/icecast/web/void.mp3':'rw' 'infiniteproject/icecast'

b5559797266c7dcd9a91f9ea8933b71fed4968ea8323ef34004e15251a3d1f5c
docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/mnt/user/appdata/icecast/icecast.xml" to rootfs at "/etc/icecast.xml": mount /mnt/user/appdata/icecast/icecast.xml:/etc/icecast.xml (via /proc/self/fd/6), flags: 0x5000: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type.

The command failed.

 

any way to fix?

10 minutes ago, diskomo said:

any way to fix?

Yep, remove the folders that the container created in the icecast folder and replace them with the files.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...