[appserver-io/appserver-io-dist/debian] libjpeg.so.8: cannot open shared object file: No such file or directory

[waja]

Looking into https://github.com/appserver-io-dist/debian/blob/master/src/generic/runtime/DEBIAN/control the dependencies seems to be solved when installing libjpeg8 or libjpeg62-turbo. Anyway, installing the (Wheezy) package on Debian Jessie (where libjpeg8 is not available) I get the following error:

Setting up appserver-dist (1.0.6-37) ...
/opt/appserver/bin/php: error while loading shared libraries: libjpeg.so.8: cannot open shared object file: No such file or directory
dpkg: error processing package appserver-dist (--configure):
 subprocess installed post-installation script returned error exit status 127
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)

It looks like /opt/appserver/bin/php is dymanical linked against libjpeg.so.8 which is provided by libjpeg8.

[wagnert]

Hi, actually we only have appserver 1.1.0 beta packages compiled for Debian Jessie. Have a look at http://builds.appserver.io and try the latest beta7 packages.

[waja]

I'm using the wheezy package in my Jessie docker image like you do in https://github.com/appserver-io-dist/docker/blob/master/appserver/1.0.6/Dockerfile#L8.

You maybe will tell me, not to use Wheezy packages on Jessie. But at least you should fix you dependencies. The truth is, with libjpeg62-turbo your dependencies are satisfied but you linked your wheezy packages against libjpeg8.

[wagnert]

We'll have a look at it tomorrow, thanks :)

[zelgerj]

Hi waja, yes you're totally right. We'll fix the dependency from libjpeg8to libjpeg62-turboas soon as possible for the debian 8 (jessie).

[zelgerj]

i've removed our deprecated docker images for 1.0.5 & 1.0.6. We'll update them in the near future. The base of those docker-images was ubuntu:latest and no debian:jessie...

To fix your problem you should do:

# BEGIN (if you have an installed appserver running)
    systemctl stop appserver
    systemctl stop appserver-php5-fpm
    systemctl stop appserver-watcher
    aptitude purge appserver-dist appserver-runtime
    rm -rf /opt/appserver
# END

rm -f /etc/apt/sources.list.d/appserver.list
echo "deb http://deb.appserver.io/ jessie main" > /etc/apt/sources.list.d/appserver.list && \
      wget http://deb.appserver.io/appserver.gpg -O - | apt-key add -
apt-get -y update
apt-get install -y appserver-dist

Successfully tested on a fresh debian jessie vm WITHOUT docker.
More infos about docker see #911

[wick-ed]

Hi @waja ,

do you still experience problems? Dependencies should have been updated.
We would like to close the issue otherwise.

Regards,

Bernhard

[waja]

@wick-ed On a fresh jessie (docker) image a apt-get install --no-install-recommends -y appserver-dist results into:

Setting up appserver-dist (1.1.0-31) ...
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)

apt-get install -y appserver-dist results into:

Setting up appserver-dist (1.1.0-31) ...
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
[...]
Errors were encountered while processing:
 appserver-dist
E: Sub-process /usr/bin/dpkg returned an error code (1)

[wick-ed]

Thanks.

This would most likely relate to this issue #911?
I would close this one then, as the issue seems to be the systemctl integration within docker as laid out by Johann in #911
We are currently in the process to refactor our docker images (not top priority though :( ). This might fix this issue.

Regards,

Bernhard

[waja]

As the package wasn't able to be installed, I can't confirm, that the shared object file problem is fixed with latest package.

[wick-ed]

I do see.
Can we go with re-opening the issue if the problem would come up again?
Why did you test with the Wheezy package in the first place?
We do offer specific Jessie packages (which share the control file with Wheezy though).

I do not understand why the missing libjpeg8 would be a problem here.

[waja]

The issue was, that you rely on a shared library libjpeg.so.8, but this was not reflected in your package dependencies. If you rely on such a library, you need depend on the (Debian) package containing this file.

[wick-ed]

I see. Did you try the Jessie package?

[waja]

Yes, I did. Just in docker: #910 (comment)

[Quix0r]

Bump up: In README.md there should be mentioned that Jessie has own packages due to dependency of libjpeg.so.8 in wheezy packages.

This one works on latest Jessie:
#910 (comment)