Thanks again for this PR @Zoey2936 ! :)

Unfortunately I am not completely sure if we should go this way since the packages that we use for talk are well tested by morph027. Switching to compiling the signaling server ourselves and using alpine as base potentially intoduces a big maintenance burden that I am not sure if I want to take...

What is your opinion on this? :)

We could copy the signaling binary out of the official image: https://hub.docker.com/r/strukturag/nextcloud-spreed-signaling
But it currently doesn't support multi arch, would this option be better for you? If yes, I create an PR on their GitHub repo, adding multi arch support.

We could copy the signaling binary out of the official image: https://hub.docker.com/r/strukturag/nextcloud-spreed-signaling
But it currently doesn't support multi arch, would this option be better for you? If yes, I create an PR on their GitHub repo, adding multi arch support.

yes, that sounds like a good approach to me, thanks :)

And should nats be pulled from alpine packages or their GitHub releases? @szaimen

And should nats be pulled from alpine packages or their GitHub releases? @szaimen

If nats is only an executable and there is an official image, we should best get it from there. Otherwise I would vote for getting it from the alpine packages.

It will now pull signaling from the signaling image, nats from the nats image and run inside the coturn image, which is alpine based, only janus will be pulled from alpine, we only need to wait that janus can be pulled from alpine inside the coturn image and strukturag/nextcloud-spreed-signaling#384 gets merged and there is a new release

It will now pull signaling from the signaling image, nats from the nats image and run inside the coturn image, which is alpine based, only janus will be pulled from alpine, we only need to wait that janus can be pulled from alpine inside the coturn image and strukturag/nextcloud-spreed-signaling#384 gets merged and there is a new release

All right, thanks a lot! :)

• https://pkgs.alpinelinux.org/package/edge/testing/x86_64/janus-gateway to be available outside testing and edge and inside coturn

I suppose this might get included in alpine 3.18 or higher then...

we could wait for coturn/coturn#1174

we could wait for coturn/coturn#1174

does this update the shipped alpine to 3.17 then?

we could wait for coturn/coturn#1174

does this update the shipped alpine to 3.17 then?

As the condition for an alpine 3.17 build was a new release, I would say yes

we could wait for coturn/coturn#1174

does this update the shipped alpine to 3.17 then?

As the condition for an alpine 3.17 build was a new release, I would say yes

Cool! Then yes, lets wait for it :)

but are there other things that need to be changed?

but are there other things that need to be changed?

only #1583 (comment) afaics

we could wait for coturn/coturn#1174

does this update the shipped alpine to 3.17 then?

As the condition for an alpine 3.17 build was a new release, I would say yes

Cool! Then yes, lets wait for it :)

how long would you say should we wait at max for this release?

we could wait for coturn/coturn#1174

does this update the shipped alpine to 3.17 then?

As the condition for an alpine 3.17 build was a new release, I would say yes

Cool! Then yes, lets wait for it :)

lets do this then in a follow-up and save the current state by merging it :)

we could wait for coturn/coturn#1174

does this update the shipped alpine to 3.17 then?

As the condition for an alpine 3.17 build was a new release, I would say yes

Cool! Then yes, lets wait for it :)

lets do this then in a follow-up and save the current state by merging it :)

yes

This is now released with v4.7.0 Beta. Testing and feedback is welcome!