-
Notifications
You must be signed in to change notification settings - Fork 538
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DNS-Resolver inside Libreoffice Docker Container Installation #385
Comments
Added to docs -- thanks. https://docs.bigbluebutton.org/2.3/install.html#package-locales-all-is-not-available |
Greetings, |
this can no longer be correct as the package bbb-libreoffice does not exis, there is only a package bbb-libreoffice-docker trying this solution did not solve the problem on Ubuntu 18.
after doing
you will not see the new nameserver there, anyhow rebooting the machine will overwrite you settings again |
I'm sorry, the correct package name is and was
That happens because in a normal systemd-resolved setup |
I still don't understand what DNS should I use inside my resolv.conf file because 10.11.12.13 clearly doesn't work and I'm still unable to install a BigBlueButton 2.3 instance. |
10.11.12.13 is not an IP you can reach, see https://en.wikipedia.org/wiki/Private_network#Private_IPv4_addresses. Just use 8.8.8.8, 1.1.1.1 or any other public dns server you like. |
The package
bbb-libreoffice-docker
tries to build a docker container and add some debian packages. For me, this failed during the installation of the package:I found out this was a name resolution issue, apt update failed to fetch the package lists (I still wonder why the Dockerfile didn't fail at that point already). The recommended Ubuntu Server 18.04 uses systemd-resolved, which presents a local caching resolver and registers this at
/etc/resolv.conf
. Docker seems to notice that that one is not reachable inside containers so it falls back to Google's DNS servers and registers them at the container's/etc/resolv.conf
. Inside our network, these are not reachable. My solution was to use our local DNS resolver directly inside the host's/etc/resolv.conf
, which will be used by docker:Do we want to add that to the Documentation? If not, this issue might still help people hitting the same problem.
The text was updated successfully, but these errors were encountered: