Univention Bugzilla – Bug 44071
systemctl daemon-reload before starting container with /etc/init.d/... start
Last modified: 2017-04-04 18:30:00 CEST
I cant install a docker in 4.2 Could not login to nextcloud. You may not be able to pull the image from the repository! 11.0.2-0: Pulling from nextcloud/univention-app-image Digest: sha256:9262b29f8954fc48392283e53a7b2df7448aa3abab2296f8c2d5559913bce931 Status: Image is up to date for nextcloud/univention-app-image:11.0.2-0 Initializing app image Preconfiguring container d7bc97973a9a290b2282acfbeb4b36613e1fa52808b488103b8ec72e15041f2a Failed to start docker-app-nextcloud.service: Unit docker-app-nextcloud.service failed to load: No such file or directory. Starting docker-app-nextcloud (via systemctl): docker-app-nextcloud.service failed! Unable to start the container! Aborting... -> /etc/init.d/docker-app-nextcloud Failed to start docker-app-nextcloud.service: Unit docker-app-nextcloud.service failed to load: No such file or directory. But after a -> systemctl daemon-reload it works. So we have to "systemctl daemon-reload" before starting the container with the init script during the installation.
r78299 (univention-appcenter 6.0.5-1A~4.2.0.201703241542): * Call 'systemctl daemon-reload' after adding a new init script (Bug #44071) r78301: * Added Bug #44071 to existing changelog entry
OK
UCS 4.2 has been released: https://docs.software-univention.de/release-notes-4.2-0-en.html https://docs.software-univention.de/release-notes-4.2-0-de.html If this error occurs again, please use "Clone This Bug".