Installation can't finish, '/usr/share/doc/jitsi-meet-web-config/config.js': No such file or directory


#1

Hi there!
I’m trying to make my own docker-container of jitsi to quickly deploy it when needed. However I can’t finish the setup due to those errors (which weren’t there before I changed to Ubuntu 18.04 I think):

...
Generating a 4096 bit RSA private key
..................................................................................................................................................++
.......................................++
writing new private key to '/etc/jitsi/meet/jitsi.domain.com.key'
-----
cp: cannot stat '/usr/share/doc/jitsi-meet-web-config/config.js': No such file or directory
dpkg: error processing package jitsi-meet-web-config (--configure):
 installed jitsi-meet-web-config package post-installation script subprocess returned error exit status 1
Setting up lua-filesystem:amd64 (1.6.3-1) ...
Setting up lua-bitop:amd64 (1.0.2-5) ...
Setting up jitsi-meet-web (1.0.3081-1) ...
Setting up lua5.1 (5.1.5-8.1build2) ...
update-alternatives: using /usr/bin/lua5.1 to provide /usr/bin/lua (lua-interpreter) in auto mode
update-alternatives: warning: skip creation of /usr/share/man/man1/lua.1.gz because associated file /usr/share/man/man1/lua5.1.1.gz (of link group lua-interpreter) doesn't exist
update-alternatives: using /usr/bin/luac5.1 to provide /usr/bin/luac (lua-compiler) in auto mode
update-alternatives: warning: skip creation of /usr/share/man/man1/luac.1.gz because associated file /usr/share/man/man1/luac5.1.1.gz (of link group lua-compiler) doesn't exist
Setting up lua-expat:amd64 (1.3.0-4) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Setting up jicofo (1.0-440-1) ...
useradd: warning: the home directory already exists.
Not copying any file from skel directory into it.
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of start.
Setting up prosody (0.10.0-1build1) ...
Adding user prosody to group ssl-cert
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of start.
Processing triggers for ca-certificates (20180409) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...

done.
done.
dpkg: dependency problems prevent configuration of jitsi-meet:
 jitsi-meet depends on jitsi-meet-web-config (= 1.0.3081-1); however:
  Package jitsi-meet-web-config is not configured yet.

dpkg: error processing package jitsi-meet (--configure):
 dependency problems - leaving unconfigured
Setting up jitsi-meet-prosody (1.0.3081-1) ...
cp: cannot stat '/usr/share/doc/jitsi-meet-prosody/prosody.cfg.lua-jvb.example': No such file or directory
dpkg: error processing package jitsi-meet-prosody (--configure):
 installed jitsi-meet-prosody package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 jitsi-meet-web-config
 jitsi-meet
 jitsi-meet-prosody

and this is what it was supposed to do:

RUN apt-get update && apt-get install apt-transport-https

RUN echo "jitsi-videobridge jitsi-videobridge/jvb-hostname string ${YOURDOMAIN}" | debconf-set-selections && \
    echo "jitsi-meet jitsi-meet/cert-choice select Self-signed certificate will be generated" | debconf-set-selections


RUN wget -qO - https://download.jitsi.org/jitsi-key.gpg.key | sudo apt-key add - && \
    sh -c "echo 'deb https://download.jitsi.org stable/' > /etc/apt/sources.list.d/jitsi-stable.list" && \
    apt-get update && apt-get install -y jitsi-meet && rm -rf /var/cache/apt /var/lib/apt/lists

Any pointers where I’ve gone wrong?

Best regards,
M


#2

What kind of environment is this? Is it a standard Debian / Ubuntu machine or VM?


#3

It’s a Docker container in an Ubuntu 16.04 VM on a proxmox (Debian) host.


#4

Are you using a “slim” image? I know for a fact it will be troublesome.

But more importantly, did you know we now have official Docker images? https://github.com/jitsi/docker-jitsi-meet

I hope that helps, cheers!


#5

Not that I know of, but I’ll check again in a bit. Why would that matter, if I add the jitsi repo, update and install the whole thing? Shouldn’t that include all dependencies?

As for the docker image: That might be an option in the future, but as of now, I need to rebuild the thing by myself.


#6

Using the “slim” base images matters, because they contain APT configuration which prevents anything from being installed in /usr/share/doc/.


#7

Ok that’s a very good reason, let me investigate and get back to you!
Best regards