Sea-Thru issue (sorry for opening here, disregard entirely if not appropriate)

[escoolioinglesias]

Hey I made a modification to the Dockerfile you made for sea-thru to use mamba and it builds very quickly:

ARG PLATFORM

FROM --platform=${PLATFORM} python:latest

# These will be pulled from the docker-compose.yml file via the `args` parameter
ARG WORKING_DIR
ARG CONDA_ENV_NAME

WORKDIR ${WORKING_DIR}

# Set some known env vars + lift from docker-compose args into env
ENV CONDA_ENV_NAME ${CONDA_ENV_NAME}
ENV CONDA_DIR /opt/conda
ENV PATH=$CONDA_DIR/bin:$PATH

# Dependencies
RUN apt-get update && apt-get install -y \
    cmake \
    build-essential \
    wget \
    gettext-base \
    ffmpeg \
    libsm6 \
    libxext6 && \
    apt-get clean

# Install miniconda and mamba
RUN wget --quiet https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh -O ~/miniconda.sh && \
    /bin/bash ~/miniconda.sh -b -p $CONDA_DIR && \
    conda install -c conda-forge mamba -y

COPY conda-environment.yml ./conda-environment-template.yml
RUN cat conda-environment-template.yml | envsubst > environment.yml

# Use mamba to create the environment
RUN mamba env create -f environment.yml
RUN echo "source activate $CONDA_ENV_NAME" > ~/.bashrc
ENV PATH $CONDA_DIR/envs/$CONDA_ENV_NAME/bin:$PATH

ADD . ${WORKING_DIR}

ENTRYPOINT ["tail", "-f", "/dev/null"]

on another Terminal i then ran
docker exec -it seathru /bin/bash

and tried:
(seathru) root@9bd05a5e822e:/opt/app# python seathru-mono-e2e.py --image /path/to/image

but got:

docker exec -it seathru /bin/bash
(seathru) root@9bd05a5e822e:/opt/app# python seathru-mono-e2e.py --image /path/to/image
Traceback (most recent call last):
  File "seathru-mono-e2e.py", line 11, in <module>
    import PIL.Image as pil
  File "/opt/conda/envs/seathru/lib/python3.6/site-packages/PIL/Image.py", line 60, in <module>
    from . import _imaging as core
ImportError: libtiff.so.5: cannot open shared object file: No such file or directory

Is libtiff5 missing as a library in the original? Any idea why this would be occuring? Is it working for you no issue?

I'm on macOS Ventura, M1 Max 64 GB

Thank you kindly, hope I'm not bothering