-
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
podman load -i Path-With-Caps label : invalid reference format: repository name must be lowercase #7337
Comments
@QiWang19 PTAL |
on Centos8 and use the code of master to compile, it works ok
|
That is not the test. If you copy-paste from my report, you will see that the test includes a label:
If you try that, I believe it will fail. |
I found the case, so
|
To match the behavior of docker-archive format, the |
after this , the image's name will be |
yes |
now load the image
In addition to modifying some code of podman, also need to modify some code of
I will try to submit changes tomorrow |
info, images, run, networking tests: remove some skip_if_remote()s that were added in the varlink days. All of these tests now seem to work with APIv2. help test: check that first output line from 'podman --help' is the program description (regression check for containers#7273). load test: clean up stray images, rewrite test to make it conform to existing convention. In the process, discover and file containers#7337 exec test (and networking): file containers#7360, and add FIXME comment to skip()s suggesting evaluating those tests once that is fixed. pod test: now that containers#6328 is fixed, use 'podman pod inspect --format' instead of relying on jq Various other tests: add an explanation of why test is disabled so we can more easily distinguish "this will never be meaningful under remote" vs "hey, doesn't work for now, but maybe someday". Signed-off-by: Ed Santiago <[email protected]>
The PR for this one seems to have stalled. |
A friendly reminder that this issue had no activity for 30 days. |
@QiWang19 @edsantiago Can we close this issue now? |
I would strongly prefer to keep this open until it is fixed. At the very absolute minimum:
$ ./bin/podman load -i /tmp/FOO/alpine.tar foo
Error: error pulling "foo": unable to pull oci:/tmp/FOO/alpine.tar:localhost/foo: error determining pull goal for image "oci:/tmp/FOO/alpine.tar:localhost/foo": error parsing dest reference name "localhost/tmp/FOO/alpine.tar": error parsing named reference "localhost/tmp/FOO/alpine.tar": invalid reference format: repository name must be lowercase
$ ./bin/podman load -i /tmp/foo/alpine.tar foo
open /tmp/foo/alpine.tar/manifest.json: not a directory
open /tmp/foo/alpine.tar/index.json: not a directory
open /tmp/foo/alpine.tar/index.json: not a directory
Error: error pulling "foo": unable to pull oci:/tmp/foo/alpine.tar:localhost/foo: Error initializing source oci:/tmp/foo/alpine.tar:localhost/foo: open /tmp/foo/alpine.tar/index.json: not a directory |
Not pass the name argument to Load API. Specify in the document the usage of the optional argument is tagging an additional image. Close containers#7337 Signed-off-by: Qi Wang <[email protected]>
Looks like containers#7337 was fixed (by containers#8112). Reenable a disabled test for it; and make it actually work. Confirmed that newly-added test fails on d456765 (the commit before containers#8112). Signed-off-by: Ed Santiago <[email protected]>
Only when
--format=oci-archive
:Only the exact sequence above fails. The following are fine:
podman save
without--format oci-archive
podman load -i /tmp/FOO.tar
withoutfoo
(label)podman save
to an all-lower-case pathEDIT: meant to add that this also fails if any directory component has caps:
/tmp/FOO/bar.tar
master @ 47108e2
The text was updated successfully, but these errors were encountered: