This PR is marked as WIP, since it depends on the distribution v3 packages which is not released yet.

Hello @jkroepke Isn't it possbile to reuse the s3 driver? and make it more generic. in theory it should work with all major cloud providers.

in theory it should work with all major cloud providers.

In practice, there is no S3 Compatibility API at Azure. The distribution project maintains an azure driver which I re-use here:

https://github.com/distribution/distribution/blob/main/docs/content/storage-drivers/azure.md

If upstream distribution project nativly support Azure, it should not be a major issue for zot? I thought, zot fully depends on it and the usage for storage driver is transparent.

in theory it should work with all major cloud providers.

In practice, there is no S3 Compatibility API at Azure. The distribution project maintains an azure driver which I re-use here:

https://github.com/distribution/distribution/blob/main/docs/content/storage-drivers/azure.md

If upstream distribution project nativly support Azure, it should not be a major issue for zot? I thought, zot fully depends on it and the usage for storage driver is transparent.

I see, understood, ok.

Let's target this for v2.1.0

Let's target this for v2.1.0

A requirement for this PR would be github.com/docker/distribution v3.0.0-alpha.1 or higher. Thats something that should not be part of the PR here.

@jkroepke I think you can make progress on this one now?

@jkroepke I think you can make progress on this one now?

I will do, but sadly it does not work out of the box and I have to investigate here whats going wrong. it will take some time.

Using Azure Tables as remote cache will be done in a separate PR.

@jkroepke do you have an update on this? or need any assistance?

Hey @rchincha

Sorry, but I have other priorities that I need to address, and it might take a while before I can return to this.

@jkroepke any updates on this? This would be useful for you and for the community at large.

Hi @rchincha

After reviewing #2584 and #724, I need to pause any further community work for now. Our initial tests did not cover signatures, but the lack of signature support could potentially cause issues in future scenarios.