GitLab

In attempting to install ldap packages in the Mayan 3.5 docker image, I get the following dependency error from apt which breaks the pip installation process for the ldap dependencies:

ryanshow@linuxapps:/opt/docker$ docker-compose up mayan-edms
postgres is up-to-date
redis is up-to-date
Creating mayan-edms ... done
Attaching to mayan-edms
mayan-edms                | mayan: starting entrypoint.sh
mayan-edms                | mayan: update_uid_gid()
mayan-edms                | usermod: no changes
mayan-edms                | mayan: os_package_installs()
mayan-edms                | Get:1 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB]
mayan-edms                | Get:2 http://deb.debian.org/debian buster InRelease [122 kB]
mayan-edms                | Get:3 http://deb.debian.org/debian buster-updates InRelease [51.9 kB]
mayan-edms                | Get:4 http://deb.debian.org/debian buster-backports InRelease [46.7 kB]
mayan-edms                | Get:5 http://security.debian.org/debian-security buster/updates/main amd64 Packages [269 kB]
mayan-edms                | Get:6 http://deb.debian.org/debian buster/main amd64 Packages [7907 kB]
mayan-edms                | Get:7 http://deb.debian.org/debian buster-updates/main amd64 Packages [9504 B]
mayan-edms                | Get:8 http://deb.debian.org/debian buster-backports/contrib Sources [5072 B]
mayan-edms                | Get:9 http://deb.debian.org/debian buster-backports/non-free Sources [9208 B]
mayan-edms                | Get:10 http://deb.debian.org/debian buster-backports/main Sources [442 kB]
mayan-edms                | Get:11 http://deb.debian.org/debian buster-backports/main amd64 Packages [458 kB]
mayan-edms                | Get:12 http://deb.debian.org/debian buster-backports/non-free amd64 Packages [34.5 kB]
mayan-edms                | Get:13 http://deb.debian.org/debian buster-backports/contrib amd64 Packages [9688 B]
mayan-edms                | Fetched 9430 kB in 2s (3925 kB/s)
mayan-edms                | Reading package lists...
mayan-edms                | Reading package lists...
mayan-edms                | Building dependency tree...
mayan-edms                | Reading state information...
mayan-edms                | Some packages could not be installed. This may mean that you have
mayan-edms                | requested an impossible situation or if you are using the unstable
mayan-edms                | distribution that some required packages have not yet been created
mayan-edms                | or been moved out of Incoming.
mayan-edms                | The following information may help to resolve the situation:
mayan-edms                |
mayan-edms                | The following packages have unmet dependencies:
mayan-edms                |  libldap2-dev : Depends: libldap-2.4-2 (= 2.4.47+dfsg-3+deb10u6) but 2.4.57+dfsg-2~bpo10+1 is to be installed
mayan-edms                | W: --force-yes is deprecated, use one of the options starting with --allow instead.
mayan-edms                | E: Unable to correct problems, you have held broken packages.
mayan-edms                | mayan: pip_installs()

Here is the relevant section from my docker-compose.yml:

  mayan-edms:
    container_name: mayan-edms
    depends_on:
      - postgres
      - redis
    environment:
      MAYAN_CELERY_BROKER_URL: redis://:@redis:6379/1
      MAYAN_CELERY_RESULT_BACKEND: redis://:@redis@6379/2
      MAYAN_DATABASE_ENGINE: django.db.backends.postgresql
      MAYAN_DATABASE_NAME: mayan
      MAYAN_DATABASE_PASSWORD: **********
      MAYAN_DATABASE_USER: mayan
      MAYAN_DATABASE_HOST: postgres
      MAYAN_PIP_INSTALLS: python-ldap django_auth_ldap
      MAYAN_APT_INSTALLS: libsasl2-dev python3-dev libldap2-dev libssl-dev libgle3 build-essential autoconf libtool pkg-config gcc
      MAYAN_SETTINGS_MODULE: mayan_settings.somenet_settings
    image: mayanedms/mayanedms:3.5.6
    networks:
      - somenet
    ports:
      - "9300:8000"
    restart: unless-stopped
    volumes:
      - "/opt/mayan:/var/lib/mayan"
      - "/mnt/somenet:/somenet_shares"

I tried looking into this a bit, I think it may have something to do with the buster-backports repo but I'm not positive. For now I've downgraded to version 3.4.22 which works fine.