As discussed during the FIWARE TSC this week, the FIWARE Foundation is considering transitioning the maintainance of its container registry from Docker Hub to Quay.io. A detailed description of the proposal can be found below. It will be discussed for acceptance at the next-but-one TSC on 8th May <>PROPOSAL The proposal is as follows: Existing historical GE images on DockerHub will be copied to quay.io/fiware for safekeeping Going forward a maintainance job could be created to copy new images from the GE Owner’s own Image Repo over to quay.io/fiware GE Owner’s image always remains the orginal source of truth - FIWARE Foundation is merely an aggregator of existing images To facilitate this information from the existing .github/fiware/config.json will be used to be able read over images using skopeo Example: { "docker": ["docker.io/telefonicaiot/iotagent-ul"], ... } would enable us to copy over: skopeo sync --src docker --dest docker \ --scoped docker.io/telefonicaiot/iotagent-ul \ quay.io/repository/fiware if this file is not present already. It will need to be added. The existing README docker badge and link will need to be amended to point to the quay.io Example: [![Docker badge](https://img.shields.io/docker/pulls/fiware/iotagent-isoxml.svg)](https://hub.docker.com/r/fiware/iotagent-isoxml/) becomes: [![Docker badge](https://img.shields.io/badge/quay.io-fiware%2Fiotagent--xml-grey?logo=red%20hat&labelColor=EE0000)](https://quay.io/repository/fiware/iotagent-isoxml) :whale: [Docker Hub](https://hub.docker.com/r/fiware/iotagent-isoxml/) <img style="height:1em" src="https://quay.io/static/img/quay_favicon.png"/> [quay.io](https://quay.io/repository/fiware/iotagent-isoxml) Where necessary, the installation documentation will need to be altered to refer to the quay.io images services: iot-agent: image: quay.io/fiware/iotagent-isoxml hostname: iot-agent container_name: fiware-iot-agent becomes: services: iot-agent: image: fiware/iotagent-isoxml hostname: iot-agent container_name: fiware-iot-agent The exsiting contributor requirements document will be amended to reflect the changes. <>ACTIONS The required action from GE Owners is as follows: Ensure that their own GE images are available and release builds can be copied Decide which Image container Registry will hold the “source of truth” Update or amend .github/fiware/config.json to reflect the correct location. { "docker": ["docker.io/telefonicaiot/iotagent-ul"], ... } Alternatively, if additional non-standard copy over processing is required, add another batch file into .github/fiware/ Example: { "dockerScript": ["path/to.script.sh"], ... } Some GEs do not currently have fiware named copies - these GEs should decide whether to offer copies to the FIWARE Foundation. <>OPTIONAL ACTIONS The existing text in the contribution requirements, requires GE Owners to produce Docker images on Docker Hub. This restriction will be loosened, so that GE Owners may use the image container registry of their own choice. It would be possible to build on gchr.io or quay.io or Docker Hub or an alternative based on company needs. <>Background Info Meeting Minutes: https://docs.google.com/document/d/1Bj-r6kXFMcySXOst2LyzMQ0U1KgyWDMnsjQrPXylLmw/ <https://docs.google.com/document/d/1Bj-r6kXFMcySXOst2LyzMQ0U1KgyWDMnsjQrPXylLmw/> Presentation: https://docs.google.com/presentation/d/1qhWRhGGooOJhBz_4w-b1dk24SHc0w8-B4iAxYojA2iw/ <https://docs.google.com/presentation/d/1qhWRhGGooOJhBz_4w-b1dk24SHc0w8-B4iAxYojA2iw/> Jason Fox Technical Evangelist Jason.fox at fiware.org <mailto:juanjose.hierro at fiware.org> www.linkedin.com/in/jason-fox-8a79563 <https://www.linkedin.com/in/jhierro> -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20230420/7c330edd/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: foundation-logo.png Type: image/png Size: 8201 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20230420/7c330edd/attachment-0001.png>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy