Univention Bugzilla – Bug 42543
Appbox based docker Apps can't be installed in an AD member mode domain
Last modified: 2016-11-08 13:26:39 CET
Currently, all UCS servers in an AD member mode domain are forced to install univention-samba during the join. As the appbox docker containers are basically member server, this also happens during the installation/join of appbox based docker apps. Problem is, the join of univention-samba in the container fails, which means the join fails, which means the app is removed. No appbox apps in AD member mode!!
Why does the join of univention-samba fail in the container? I think we shouldn't install univention-samba in case it is the appbox image.
(In reply to Stefan Gohmann from comment #1) > Why does the join of univention-samba fail in the container? > I guess the join fails due to the 'samba inside docker' can't reach the MS-AD.
My initial guess would be that we don't set all UCR variables required to generate a valid smb.conf in the container. According to leading Appcenter developers we currently selectively copy this list of UCR variables from the host: ['nameserver.*', 'repository/online/server', 'repository/app_center/server', 'update/secure_apt', 'appcenter/index/verify', 'ldap/master.*', 'locale.*', 'domainname']
OTOH (at least in the long term) it may also be required to instruct docker run to expose a couple of samba ports to the outside, something like -p 138:138/udp -p 139:139 -p 445:445 -p 445:445/udp
*** This bug has been marked as a duplicate of bug 40611 ***
Created attachment 8145 [details] dont_configure_ad_member_mode_in_appbox_container.patch This would add some heuristic to univention-join to detect an appbox container. We could also move this to base/univention-lib/shell/admember.sh instead.
OK, duplicate.
UCS 4.1-4 has been released: https://docs.software-univention.de/release-notes-4.1-4-en.html https://docs.software-univention.de/release-notes-4.1-4-de.html If this error occurs again, please use "Clone This Bug".