You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks a bit confusing because the file has also been pushed to v12 and v13, but the logs don't tell me this result explicitly.
What did you expect to happen?
$ oras push localhost:5000/oras:v11,v12,v13 hello.txt
Exists e3b0c44298fc hello.txt
Tagged v11 and pushed the file to [registry] localhost:5000/oras:v11
Tagged v12 and pushed the file to [registry] localhost:5000/oras:v12
Tagged v13 and pushed the file to [registry] localhost:5000/oras:v13
Digest: sha256:466a0ca65eff1b3602f5ef44cf6e32bac75976ccbdacf3d7c09218a5cd2db373
or
$ oras push localhost:5000/oras:v11,v12,v13 hello.txt
Exists e3b0c44298fc hello.txt
pushed the file to [registry] localhost:5000/oras:v11
pushed the file to [registry] localhost:5000/oras:v12
pushed the file to [registry] localhost:5000/oras:v13
Digest: sha256:466a0ca65eff1b3602f5ef44cf6e32bac75976ccbdacf3d7c09218a5cd2db373
How can we reproduce it?
Described in the first question
What is the version of your ORAS CLI?
v1.1.0
What is your OS environment?
Ubuntu
Are you willing to submit PRs to fix it?
Yes, I am willing to fix it.
The text was updated successfully, but these errors were encountered:
oras push localhost:5000/oras:v11,v12,v13 hello.txt = oras push localhost:5000/oras:v11 hello.txt + orag tag localhost:5000/oras:v11, the Tagged xxx output is just to be consistent with oras tag logs.
FeynmanZhou
changed the title
The logs is not matched with the result when pushing a file with multiple tags
ORAS log is not matched with the result when pushing a file with multiple tags
Dec 26, 2023
@FeynmanZhou is this really needed? As @qweeah has mentioned, the current output is by design.
It is not appropriate to print something like
Tagged v11 and pushed the file to [registry] localhost:5000/oras:v11
Tagged v12 and pushed the file to [registry] localhost:5000/oras:v12
Tagged v13 and pushed the file to [registry] localhost:5000/oras:v13
, because of the following reasons:
The file is pushed as a layer, not a manifest, and it can't be represented by a tag such as v11
If the push target is an OCI layout, what ORAS does behind the scenes is pushing the manifest first and tagging them
What happened in your environment?
I pushed a file
hello.txt
with 3 tagsv11
,v12
,v13
as follows:From the logs, it tells me the file has been pushed to only, but v12 and v13 are tagged.
Next, when I view the manifest of
localhost:5000/oras:v12
, the filehello.txt
has also been pushed to this repo.It looks a bit confusing because the file has also been pushed to v12 and v13, but the logs don't tell me this result explicitly.
What did you expect to happen?
or
How can we reproduce it?
Described in the first question
What is the version of your ORAS CLI?
v1.1.0
What is your OS environment?
Ubuntu
Are you willing to submit PRs to fix it?
The text was updated successfully, but these errors were encountered: