Closed ReimarBauer closed 2 months ago
ReimarBauer
commented
11 months ago Could here be a difference between miniforge3 and mambaforge containers?
I tried to reproduce this in a local miniforge3 container with a recent 1.5.5 mamba and can't. So I'm unsure what the problem in my production setup is. Without that problem I would have changed already to miniforge3. Any ideas if there could be a relation what container I use?
thawn
commented
11 months ago I am seeing the same issue in a singularity container (based on the docker container nvidia/cuda:11.3.1-base-ubuntu20.04)
during container creation, I do set up the locales like this:
apt-get install -y -q locales
apt-get clean -q
export LANGUAGE="en_US.UTF-8"
export LANG="en_US.UTF-8"
export LC_ALL="en_US.UTF-8"
echo "LC_ALL=en_US.UTF-8" >> /etc/environment
echo "en_US.UTF-8 UTF-8" >> /etc/locale.gen
echo "LANG=en_US.UTF-8" > /etc/locale.conf
locale-gen --purge en_US.UTF-8
dpkg-reconfigure --frontend=noninteractive locales
jjerphan
commented
2 months ago Hi @ReimarBauer,
I cannot reproduce this issue. I am assuming this has been fixed in the meantime.
If it has not, feel free to open an issue upstream with a minimal reproducer.
ReimarBauer
commented
2 months ago I missed to comment here.
This looks solved in the mamba 1.5.5. version, maybe also earlier. Can't reproduce in my local docker miniforge3 container too.
Solution to issue cannot be found in the documentation.
Issue
xmlschema got an update 10 days ago to 2.5.0
We use the docker image condaforge/mambaforge and installing dependencies of our packages fail with
Installed packages