[new-feature]: Docker Image for Asterisk

[urpylka]

Feature Description

Hi, I know a few docker images for Asterisk it is simply looking for by the query on dockerhub. But there is no an official image. Will it be maintained officially by core team of Asterisk.

Now there is no actual version of software in the current images and more value there is no common practices to work with, there is also no main approach to set of software and methods to install dependencies.

And I didn't say a word about how to complicated to deploy Asterisk and about main benefits of Dockerize (containerize) applications.

Maybe I missed, and it exists. But if no, maybe there will be a good decision to move a type of delivery your application into containerized. What do you think?

Thanks

[jcolp]

There is no official image. There was an attempt, but noone could agree on what such a thing would look like, how it would work, how it would be configured. Moving into a container also increases the complexity from a networking perspective, and is something that I've seen most people encounter when deploying using it without understanding SIP.

[jcolp]

I have also moved this to the feature requests repository.

[urpylka]

For start: Let's list (in a free form) all bugs/issues/questions with the migration to the Docker image (if there is link to previous attempts) lets mention it here. Suppose it can help, not only for us, but and for other people how will attempt to do something by ourself.

I mean the problem with SIP that you mentioned. Maybe for some cases a container trully doesn't fit. But it is good when we "planar" understand reason for it.

[jcolp]

I don't have any links to previous attempts. Others may be able to chime in with their experiences.

[zombiedk]

Hi I woulden mind giving it a try, as I already have several Dockerfile's for building asterisk

General idear:

• asterisk (build asterisk)
• asterisk-full (build asterisk + soundfiles) ; populate /var/lib/asterisk/sounds/
• asterisk-debug (build on top of asterisk and then include tools [asterisk-lint,sngrep,tcpdump,sipp,vim,...])
• asterisk-test (build asterisk to comply with testsuite requirements and include testuite)

  include a deply script what will populate /etc/asterisk for any missing files, in order to handle volume support

[vk496]

+1 for this.

Having trigger/init scripts during the container start would allow people to extend with the features they need without arguing which is the correct way of doing it.

My idea of perfect asterisk image:

• One tag pointing to the Asterisk version (less complexity to maintain) with all possible modules built inside.
• ENV var to set a list of modules to enable, with a default value
• Default config. User can override config through volumes if needed
• A /docker-entrypoint-init.d folder that run every script available there
• Multiarch

If someone from core team want to support this idea, please let me know. I can create a PR