-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[Windows] podman machine > podman export error #15247
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
remote
Problem is in podman-remote
windows
issue/bug on Windows
Comments
github-actions
bot
added
remote
Problem is in podman-remote
windows
issue/bug on Windows
labels
Aug 9, 2022
@n1hility PTAL |
@mheon this really has nothing to do with machine (i think). we should look at it. ill poke it now |
Yeah, this is probably just a path validation portability issue. Sorry I had not had time to look at it. I have a full plate atm. Thanks for taking a look @baude |
(BTW promise as soon as I finish this major win installer revamp, I will dive into my backlog) |
baude
added a commit
to baude/podman
that referenced
this issue
Aug 24, 2022
the `podman save` command was failing on windows due to the use of a colon between the drive letter and first directory. the check was intended for Linux and not windows. Fixes containers#15247 [NO NEW TESTS NEEDED] Signed-off-by: Brent Baude <[email protected]>
openshift-cherrypick-robot
pushed a commit
to openshift-cherrypick-robot/podman
that referenced
this issue
Aug 29, 2022
the `podman save` command was failing on windows due to the use of a colon between the drive letter and first directory. the check was intended for Linux and not windows. Fixes containers#15247 [NO NEW TESTS NEEDED] Signed-off-by: Brent Baude <[email protected]>
mheon
pushed a commit
to mheon/libpod
that referenced
this issue
Sep 6, 2022
the `podman save` command was failing on windows due to the use of a colon between the drive letter and first directory. the check was intended for Linux and not windows. Fixes containers#15247 [NO NEW TESTS NEEDED] Signed-off-by: Brent Baude <[email protected]>
github-actions
bot
added
the
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
label
Sep 18, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
remote
Problem is in podman-remote
windows
issue/bug on Windows
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
When trying to export a container to a tar.gz file on Windows (using
podman machine
as the backend), there's an error about the:
due to the Windows path.The
\
are correctly escaped but not the:
.Steps to reproduce the issue:
All steps below are done in Powershell
As a workaround, here is a different Windows path that works:
Describe the results you received:
The export results in the following error (based on the example above):
Error: invalid filename (should not contain ':') "C:\\wslsources\\fedora-latest.tar.gz"
Describe the results you expected:
The container is exported successfully and the file created.
Additional information you deem important (e.g. issue happens only occasionally):
N/A
Output of
podman version
:Output of
podman info
:Package info (e.g. output of
rpm -q podman
orapt list podman
):N/A -> using the default
podman machine
setup.Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
Podman on Windows using WSL2
The text was updated successfully, but these errors were encountered: