Describe the Bug
In many Dockerfiles, we have this pattern:
RUN git clone --depth 1 https://github.com/asdf-vm/asdf.git $HOME/.asdf
ENV PATH="/root/.asdf/shims:/root/.asdf/bin:${PATH}"
RUN for x in $(sed -e '/^\s*#.*$/d' -e '/^\s*$/d' <.tool-versions | cut -f1 -d ' '); \
do \
/root/.asdf/bin/asdf plugin add $x; \
/root/.asdf/bin/asdf install $x; \
done
The error was: /root/.asdf/bin/asdf: not found
This has worked well for a long time. Yesterday it started failing, we think after #1822.
When we close a specific, older commit instead like this:
RUN git clone --no-checkout https://github.com/asdf-vm/asdf.git $HOME/.asdf && \
cd $HOME/.asdf && \
git fetch --depth 1 origin 6a97697d3d88d6b7ad19c4bd3157679b052ab657 && \
git checkout FETCH_HEAD
It starts working again.
Steps to Reproduce
Exact steps are shown above
Expected Behaviour
Either:
- Preserve the original clone behavior
- Explain how to map the old behavior to new
Actual Behaviour
Error: /root/.asdf/bin/asdf: not found
Environment
Running in `public.ecr.aws/docker/library/python:3.10.8-slim-buster`
asdf plugins affected (if relevant)
No response
Describe the Bug
In many Dockerfiles, we have this pattern:
The error was:
/root/.asdf/bin/asdf: not foundThis has worked well for a long time. Yesterday it started failing, we think after #1822.
When we close a specific, older commit instead like this:
It starts working again.
Steps to Reproduce
Exact steps are shown above
Expected Behaviour
Either:
Actual Behaviour
Error:
/root/.asdf/bin/asdf: not foundEnvironment
asdf plugins affected (if relevant)
No response