[appserver-io/appserver-io-dist/debian] Failed to get D-Bus connection: Unknown error -1

[waja]

Installing appserver-dist from deb http://deb.appserver.io/ jessie main on Jessie results into:

Setting up appserver-dist (1.0.6-13) ...
Setup for mode 'install' done successfully!
Failed to get D-Bus connection: Unknown error -1
dpkg: error processing package appserver-dist (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for libc-bin (2.19-18+deb8u1) ...
Errors were encountered while processing:
 appserver-dist
E: Sub-process /usr/bin/dpkg returned an error code (1)

[wagnert]

Here it's the same, we only have appserver 1.1.0 beta packages for Debian Jessie actually.

[waja]

It seems you have appserver-dist 1.0.6-13 and appserver-runtime 1.0.7-27 in your suite 'jessie' accordingly http://deb.appserver.io/dists/jessie/main/binary-amd64/Packages. Maybe I'll look into the beta packages too.

[zelgerj]

The systemctl command talks to systemd over a DBus connection. It is unlikely that you are running systemd in your container, so systemctl has nothing with which to talk.

While it is possible to run systemd in a container, doing so is often (but not always!) a sign that you need to rethink the architecture of your containers.

As mentioned in #910 we removed our deprecated docker-images for appserver 1.0.5 & 1.0.6 because we have to refactor it to be in proper use of the docker-container system. In a couple of days we'll provide the refactored docker-images to run the appserver within a docker-container like it should.