Skip to content
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

Release 3.7.0 tag is missing on docker hub #4154

Closed
Siedlerchr opened this issue Jun 27, 2022 · 7 comments
Closed

Release 3.7.0 tag is missing on docker hub #4154

Siedlerchr opened this issue Jun 27, 2022 · 7 comments
Labels

Comments

@Siedlerchr
Copy link

Bug description

I wanted to test version 3.7.0, however on docker hub there is no release tagged with 3.7.0. I only find releases tagged with 3.70-PRE
https://hub.docker.com/r/fiware/orion/tags?page=1&name=3.7

@Siedlerchr Siedlerchr added the bug label Jun 27, 2022
@fgalan
Copy link
Member

fgalan commented Jun 27, 2022

Not sure why it's not working... @wistefan could you have a look, please?

In the meanwhile, you can use telefonicaiot/fiware-orion:3.7.0

@Siedlerchr
Copy link
Author

It's still not there... But the the telefonicaiot/fiware-orion:3.7.0 worked

@fgalan
Copy link
Member

fgalan commented Aug 18, 2022

Great!

Based on the feedback, I'll close the issue. However, please feel free of contacting FIWARE Foundation (@wistefan @jason-fox ...) regarding the sync problems in fiware dockerhub organization.

@fgalan fgalan closed this as completed Aug 18, 2022
@jason-fox
Copy link
Contributor

jason-fox commented Aug 18, 2022

Since Docker removed the ability for a third-party to listen to releases and automate builds, the fiware docker tags will always lag the original source of truth. telefonicaiot needs to build and tag an image first, fiware is just an aggregator of existing Docker images. This is the case for telefonicaiot, but it is also true for all other components aggregated from the FIWARE Catalogue. The only time that the latest telefonicaiot tag can be assured to be duplicated on the fiware account is just prior to an umbrella FIWARE release.

Anyway I pushed off a sync process and fiware/orion:3.7.0 can also be used at this point.

@Siedlerchr
Copy link
Author

Siedlerchr commented Aug 18, 2022

@jason-fox Thanks! Can you check the same for the ging/fiware-idm and ging/fiware-pep? The newest 8.2 release is also not available
ging/fiware-pep-proxy#141

@jason-fox
Copy link
Contributor

Can you check the same for the ging/fiware-idm and ging/fiware-pep? The newest 8.2 release is also not available

I have no access to the GING Docker account

@fgalan
Copy link
Member

fgalan commented Aug 18, 2022

Since Docker removed the ability for a third-party to listen to releases and automate builds, the fiware docker tags will always lag the original source of truth. telefonicaiot needs to build and tag an image first, fiware is just an aggregator of existing Docker images. This is the case for telefonicaiot, but it is also true for all other components aggregated from the FIWARE Catalogue. The only time that the latest telefonicaiot tag can be assured to be duplicated on the fiware account is just prior to an umbrella FIWARE release.

If fiware dockerhub cannot keep sync with the "sources of truth" :), maybe fiware dockerhub organization should be disabled and removed. Otherwise, we will have more issues like the one that @Siedlerchr reports here, causing confusion in our users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants