[WORK IN PROGRESS] Feature/jitsi meet docker single image #234
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a WIP PR for enabling Jitsi in Amnezia.
This main complexity of this task comes from not-so-trivial modular setup of Jitsi: there's no standalone Jitsi image, officially Jitsi Meet is distributed via docker-compose.yml.
Strictly speaking this approach of moving from docker-compose.yml to just
Dockerfile
+run_container.sh
requires reverse engineering of Jitsi, although even with the current state ofDockerfile
andrun_container.sh
there is a moderate progress: what's needed to be done is to verify the installed image works as expected.So far the main culprit is setting up Prosody XMPP server which is is a part of
docker-compose
-based official distribution. Whether Prosody can be removed from the setup is yet not clear.Other ideas:
docker-compose
in Amneziaapt-get
) in the build time