Skip to content

Add missing volume mounts for coturn and redis#370

Merged
alangecker merged 1 commit intobigbluebutton:developfrom
matthijskooijman:add-missing-volumes
Jan 7, 2026
Merged

Add missing volume mounts for coturn and redis#370
alangecker merged 1 commit intobigbluebutton:developfrom
matthijskooijman:add-missing-volumes

Conversation

@matthijskooijman
Copy link
Contributor

These directories were marked as volumes in their dockerfile, but nothing was explicitly mounted on them. This makes docker create an unnamed volume and mount that when the container is created, which means that on every down/up cycle, it would leave two unnamed volumes lingering around.

Explicitly mounting these data directories prevents this.

These directories were marked as volumes in their dockerfile, but
nothing was explicitly mounted on them. This makes docker create an
unnamed volume and mount that when the container is created, which means
that on every down/up cycle, it would leave two unnamed volumes
lingering around.

Explicitly mounting these data directories prevents this.
@alangecker
Copy link
Collaborator

ah, good point! I wasn't aware about that docker behavior.

Thanks for the PR!

@alangecker alangecker merged commit 2114d71 into bigbluebutton:develop Jan 7, 2026
@matthijskooijman
Copy link
Contributor Author

Thanks!

I actually recently came across this post, https://stackoverflow.com/a/62068396/740048, which argues to just not ever use VOLUME in your Dockerfile at all, because of this particularly (actually useless) behavior in docker. I'll leave that for your consideration :-)

@alangecker alangecker mentioned this pull request Jan 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants