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
What is the version of your Accelerated Container Image
No response
What would you like to be added?
I was trying out userspace conversion, and it seems the conversion works on an image in a remote registry, and the converted image is also in the remote image registry. If I have an image in my local store, and want to convert it and keep the converted image in the local store, I don't see an option to do that.
This command works and the converted image is pushed to the remote registry:
ERRO[0000] failed to create overlaybd builder: failed to resolve reference "overlaybd/redis:6.2.6": failed to do request: Head "https://overlaybd/v2/redis/manifests/6.2.6": dial tcp: lookup overlaybd on 127.0.0.53:53: server misbehaving
Is this expected?
Why is this needed for Accelerated Container Image?
Ask to support converting an image from the local image image store in the userspace.
Are you willing to submit PRs to contribute to this feature?
Yes, I am willing to implement it.
The text was updated successfully, but these errors were encountered:
What is the version of your Accelerated Container Image
No response
What would you like to be added?
I was trying out userspace conversion, and it seems the conversion works on an image in a remote registry, and the converted image is also in the remote image registry. If I have an image in my local store, and want to convert it and keep the converted image in the local store, I don't see an option to do that.
This command works and the converted image is pushed to the remote registry:
If I have an image in my local store, and try to convert it, it doesn't work:
I got an error like:
Is this expected?
Why is this needed for Accelerated Container Image?
Ask to support converting an image from the local image image store in the userspace.
Are you willing to submit PRs to contribute to this feature?
The text was updated successfully, but these errors were encountered: