Prosody Dockerfile update issue

We were using jitsi docker since the stable versions (since january stable-4101 maybe) and didn’t pull the recent updates. I was shifting our previous video server to another today and found out that the previous Prosody Dockerfile is getting error while building image for Prosody. The error is :

"mv: cannot stat ‘/tmp/usr/share/jitsi-meet/prosody-plugins’: No such file or directory"

prosody dockerfile (I just added some few lines at the end for my purpose)
ARG JITSI_REPO=jitsi
FROM ${JITSI_REPO}/base

RUN \
    apt-dpkg-wrap apt-get update \
    && apt-dpkg-wrap apt-get install -t stretch-backports -y \
      prosody \
      liblua5.2-dev \
      sasl2-bin \
      libsasl2-modules-ldap \
      libsasl2-dev \
      libssl1.0-dev \
      lua-basexx \
      lua-ldap \
      luarocks \
      git \
      gcc \
      patch \
    && luarocks install cyrussasl 1.1.0-1 \
    && luarocks install lua-cjson 2.1.0-1 \
    && luarocks install luajwtjitsi 1.3-7 \
    && luarocks install net-url 0.9-1 \
    && apt-dpkg-wrap apt-get remove -t stretch-backports -y \
      git \
      gcc \
      luarocks \
      libsasl2-dev \
      libssl1.0-dev \
      liblua5.2-dev \
    && apt-cleanup \
    && rm -rf /etc/prosody /var/cache/apt

RUN \
    apt-dpkg-wrap apt-get update \
    && apt-dpkg-wrap apt-get -d install -y jitsi-meet-tokens \
    && dpkg -x /var/cache/apt/archives/jitsi-meet-tokens*.deb /tmp \
    && mv /tmp/usr/share/jitsi-meet/prosody-plugins /prosody-plugins \
    && apt-cleanup \
    && rm -rf /tmp/usr /var/cache/apt

RUN \
    sed -i s/hook/hook_global/g /prosody-plugins/mod_auth_token.lua \
    && patch -d /usr/lib/prosody/modules/muc -p0 < /prosody-plugins/muc_owner_allow_kick.patch\
    && rm /prosody-plugins/mod_muc_size.lua
    
COPY mod_muc_size.lua /prosody-plugins/
COPY rootfs/ /

EXPOSE 5222 5269 5347 5280

VOLUME ["/config", "/prosody-plugins-custom"]

even my prosody image from this dockerfile is working in our staging server (image built months ago) but isn’t working on new machines (no cache) how can I solve this issue ? though other jvb,jicofo,web dockerfile’s is not getting error. may be there has been some changes in debian packages?
should we use new updated prosody dockerfile and are all new updates in docker stable so we can just use these ? @saghul
Thanx in advance :heart:

Yes, the package name changed: https://github.com/jitsi/docker-jitsi-meet/blob/b235ea12616803e93eac47aeecfcc3eacac3ba21/prosody/Dockerfile#L45

1 Like

Thanx for the reply… so should I just use the new prosody dockerfile or just the updated version of previous u gave?
actually are there major changes in other docker images and should I pull those for better performance and are they stable?

Rule of thumb: run the latest (and the greatest!) :slight_smile:

1 Like

yeah… I was just concerned that is there any major changes that can affect the previous stable environment or may cause unnecessary problems :3 and thanx for the info :heart: