-
Notifications
You must be signed in to change notification settings - Fork 766
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support relative mountpoints when building #4309
Comments
A friendly reminder that this issue had no activity for 30 days. |
This is still a issue |
I'll check this thanks. |
A friendly reminder that this issue had no activity for 30 days. |
Still a issue |
@flouthoc any update? |
flouthoc
added a commit
to flouthoc/buildah
that referenced
this issue
Dec 7, 2022
When working with `--mount=type=bind` and `--mount=type=cache` allow `target` to accept relative paths w.r.t to the configured work dir. Closes: containers#4309 Signed-off-by: Aditya R <arajan@redhat.com>
THanks PR #4452 should close this. |
flouthoc
added a commit
to flouthoc/buildah
that referenced
this issue
Dec 8, 2022
When working with `--mount=type=bind` and `--mount=type=cache` allow `target` to accept relative paths w.r.t to the configured work dir. Closes: containers#4309 Signed-off-by: Aditya R <arajan@redhat.com>
flouthoc
added a commit
to flouthoc/buildah
that referenced
this issue
Dec 14, 2022
When working with `--mount=type=bind` and `--mount=type=cache` allow `target` to accept relative paths w.r.t to the configured work dir. Closes: containers#4309 Signed-off-by: Aditya R <arajan@redhat.com>
flouthoc
added a commit
to flouthoc/buildah
that referenced
this issue
Dec 15, 2022
When working with `--mount=type=bind` and `--mount=type=cache` allow `target` to accept relative paths w.r.t to the configured work dir. Closes: containers#4309 Signed-off-by: Aditya R <arajan@redhat.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently when using
nixpacks
with the docker shim(andBUILDAH_FORMAT=docker
) the build fails as it complains that there is an invalid container path which is relative to the working directory. I have verified this behavior is present in docker and I believe in an effort to maintain compatibility should also be present in buildah\podman.Steps to reproduce the issue:
(these are taken directly from nixpack output
--mount=type=cache,id=YfHI60aApFM-target,target=target
Describe the results you received:
throws error
error resolving mountpoints for container "container id": invalid container path "target", must be an absolute path
Describe the results you expected:
no error and continue in build
Output of
pacman -Q
:Output of
buildah version
:Output of
podman version
if reporting apodman build
issue:Output of
cat /etc/*release
:Output of
uname -a
:Output of
cat /etc/containers/storage.conf
:The text was updated successfully, but these errors were encountered: