I'm trying to build a set of docker comntainers using docker compose, and for some reason, it will not work on one host machine.
I recently deployed the containers on a new system and have had no issues building, but when I went back to an old system that previously had the containers running and pulled in the latest changes to build, I started getting the following error:
0.360 info libmamba ****************** Backtrace Start ******************
0.360 debug libmamba Loading configuration
0.360 trace libmamba Compute configurable 'create_base'
0.360 trace libmamba Compute configurable 'no_env'
0.360 trace libmamba Compute configurable 'no_rc'
0.360 trace libmamba Compute configurable 'rc_files'
0.360 trace libmamba Compute configurable 'root_prefix'
0.360 trace libmamba Get RC files configuration from locations up to HomeDir
0.360 trace libmamba Configuration not found at '/home/mambauser/.mambarc'
0.360 trace libmamba Configuration not found at '/home/mambauser/.mamba/mambarc.d'
0.360 trace libmamba Configuration not found at '/home/mambauser/.mamba/mambarc'
0.360 trace libmamba Configuration not found at '/home/mambauser/.mamba/.mambarc'
0.360 trace libmamba Configuration not found at '/home/mambauser/.config/mamba/mambarc.d'
0.360 trace libmamba Configuration not found at '/home/mambauser/.config/mamba/mambarc'
0.360 trace libmamba Configuration not found at '/home/mambauser/.config/mamba/.mambarc'
0.360 trace libmamba Configuration not found at '/home/mambauser/.condarc'
0.360 trace libmamba Configuration not found at '/home/mambauser/.conda/condarc.d'
0.360 trace libmamba Configuration not found at '/home/mambauser/.conda/condarc'
0.360 trace libmamba Configuration not found at '/home/mambauser/.conda/.condarc'
0.360 trace libmamba Configuration not found at '/home/mambauser/.config/conda/condarc.d'
0.360 trace libmamba Configuration not found at '/home/mambauser/.config/conda/condarc'
0.360 trace libmamba Configuration not found at '/home/mambauser/.config/conda/.condarc'
0.360 trace libmamba Configuration not found at '/opt/conda/.mambarc'
0.360 trace libmamba Configuration not found at '/opt/conda/condarc.d'
0.360 trace libmamba Configuration not found at '/opt/conda/condarc'
0.360 trace libmamba Configuration not found at '/opt/conda/.condarc'
0.360 trace libmamba Configuration not found at '/var/lib/conda/.mambarc'
0.360 trace libmamba Configuration not found at '/var/lib/conda/condarc.d/'
0.360 trace libmamba Configuration not found at '/var/lib/conda/condarc'
0.360 trace libmamba Configuration not found at '/var/lib/conda/.condarc'
0.360 trace libmamba Configuration not found at '/etc/conda/.mambarc'
0.360 trace libmamba Configuration not found at '/etc/conda/condarc.d/'
0.360 trace libmamba Configuration not found at '/etc/conda/condarc'
0.360 trace libmamba Configuration not found at '/etc/conda/.condarc'
0.360 trace libmamba Update configurable 'no_env'
0.360 trace libmamba Compute configurable 'envs_dirs'
0.360 trace libmamba Compute configurable 'file_specs'
0.360 error libmamba YAML error in spec file '/app/chat_environment.yml'
0.360 critical libmamba bad file: /app/chat_environment.yml
0.360 info libmamba ****************** Backtrace End ********************
------
Dockerfile.tools:7
--------------------
6 | COPY tools_environment.yml .
7 | >>> RUN micromamba install -f tools_environment.yml -y && \
8 | >>> micromamba clean --all --yes
9 |
--------------------
target tools: failed to solve: process "/usr/local/bin/_dockerfile_shell.sh micromamba install -f tools_environment.yml -y && micromamba clean --all --yes" did not complete successfully: exit code: 1
Note: You can disregard the discrepancy between "tools" and "chat" here. There are two containers that are both based on micromamba, and one is called tools and one is called chat. They are both exhibiting the same issue. It looks like the part of the error I copied references both in a way that makes it look like Dockerfile.tools has a reference to chat, but it does not.
I inherited this code from another developer who recently left the company, and I have not had experience with docker before this. All I can tell you is that there is literally no code or config difference between the two machines (aside from port numbers) but it will not build on this one. The error is vague and only seems to imply that the yml file is not in spec somehow.
Here is the Dockerfile and the yml file:
FROM mambaorg/micromamba:2.4-debian12-slim
WORKDIR /app
# Install environment
COPY chat_environment.yml .
RUN micromamba install -f chat_environment.yml -y && \
micromamba clean --all --yes
# Copy project files
COPY . .
RUN rm chat_environment.yml
# Expose FastAPI port
EXPOSE 5001
# Run FastAPI server with uvicorn
CMD ["uvicorn", "chat_server:app", "--host", "0.0.0.0", "--port", "5001"]
name: chat
channels:
- conda-forge
dependencies:
- _libgcc_mutex=0.1=conda_forge
- _openmp_mutex=4.5=2_gnu
- annotated-types=0.7.0=pyhd8ed1ab_1
- anyio=4.10.0=pyhe01879c_0
- brotli-python=1.1.0=py313h46c70d0_3
- bzip2=1.0.8=h4bc722e_7
- ca-certificates=2025年8月3日=hbd8a1cb_0
- certifi=2025年8月3日=pyhd8ed1ab_0
- cffi=1.17.1=py313hfab6e84_0
- charset-normalizer=3.4.3=pyhd8ed1ab_0
- click=8.2.1=pyh707e725_0
- dnspython=2.7.0=pyhff2d567_1
- email-validator=2.2.0=pyhd8ed1ab_1
- email_validator=2.2.0=hd8ed1ab_1
- exceptiongroup=1.3.0=pyhd8ed1ab_0
- fastapi=0.116.1=h26c32bb_1
- fastapi-cli=0.0.8=pyhd8ed1ab_0
- fastapi-core=0.116.1=pyhe01879c_1
- h11=0.16.0=pyhd8ed1ab_0
- h2=4.2.0=pyhd8ed1ab_0
- hpack=4.1.0=pyhd8ed1ab_0
- httpcore=1.0.9=pyh29332c3_0
- httptools=0.6.4=py313h536fd9c_0
- httpx=0.28.1=pyhd8ed1ab_0
- hyperframe=6.1.0=pyhd8ed1ab_0
- idna=3.10=pyhd8ed1ab_1
- jinja2=3.1.6=pyhd8ed1ab_0
- ld_impl_linux-64=2.44=h1423503_1
- libexpat=2.7.1=hecca717_0
- libffi=3.4.6=h2dba641_1
- libgcc=15.1.0=h767d61c_4
- libgcc-ng=15.1.0=h69a702a_4
- libgomp=15.1.0=h767d61c_4
- liblzma=5.8.1=hb9d3cd8_2
- libmpdec=4.0.0=hb9d3cd8_0
- libsqlite=3.50.4=h0c1763c_0
- libstdcxx=15.1.0=h8f9b012_4
- libuuid=2.38.1=h0b41bf4_0
- libuv=1.51.0=hb03c661_1
- libzlib=1.3.1=hb9d3cd8_2
- markdown-it-py=4.0.0=pyhd8ed1ab_0
- markupsafe=3.0.2=py313h8060acc_1
- mdurl=0.1.2=pyhd8ed1ab_1
- ncurses=6.5=h2d0b736_3
- openssl=3.5.2=h26f9b46_0
- pip=25.2=pyh145f28c_0
- pycparser=2.22=pyh29332c3_1
- pydantic=2.11.7=pyh3cfb1c2_0
- pydantic-core=2.33.2=py313h4b2b08d_0
- pygments=2.19.2=pyhd8ed1ab_0
- pysocks=1.7.1=pyha55dd90_7
- python=3.13.5=hec9711d_102_cp313
- python-dotenv=1.1.1=pyhe01879c_0
- python-multipart=0.0.20=pyhff2d567_0
- python_abi=3.13=8_cp313
- pyyaml=6.0.2=py313h8060acc_2
- readline=8.2=h8c095d6_2
- requests=2.32.5=pyhd8ed1ab_0
- rich=14.1.0=pyhe01879c_0
- rich-toolkit=0.15.0=pyhe01879c_0
- shellingham=1.5.4=pyhd8ed1ab_1
- sniffio=1.3.1=pyhd8ed1ab_1
- starlette=0.47.3=pyhfdc7a7d_0
- tk=8.6.13=noxft_hd72426e_102
- typer=0.16.1=pyhc167863_0
- typer-slim=0.16.1=pyhe01879c_0
- typer-slim-standard=0.16.1=h810d63d_0
- typing-extensions=4.14.1=h4440ef1_0
- typing-inspection=0.4.1=pyhd8ed1ab_0
- typing_extensions=4.14.1=pyhe01879c_0
- tzdata=2025b=h78e105d_0
- urllib3=2.5.0=pyhd8ed1ab_0
- uvicorn=0.35.0=pyh31011fe_0
- uvicorn-standard=0.35.0=h31011fe_0
- uvloop=0.21.0=py313h536fd9c_1
- watchfiles=1.1.0=py313h920b4c0_0
- websockets=15.0.1=py313h536fd9c_0
- yaml=0.2.5=h280c20c_3
- zstandard=0.23.0=py313h07c4f96_3
What could I look at?
1 Answer 1
It turns out that the problem was caused by filesystem permissions. Docker is running as root and the file had 660 permissions.