|
|
# ESCAPE docker-hub / registry
|
|
|
|
|
|
Collection of ESCAPE docker containers as proof of concept without waiting for a EOSC hub Docker-hub? Gitlab registry?
|
|
|
|
|
|
[https://gitlab.in2p3.fr/escape2020/wp3/ossr-registry](https://gitlab.in2p3.fr/escape2020/wp3/ossr-registry)
|
|
|
|
|
|
## who should provide the containers / images ?
|
|
|
|
|
|
* software provider
|
|
|
* need to link ossr records to their containers to find them
|
|
|
* through metadata?
|
|
|
* how?
|
|
|
* having a list of containers is more complicated (many sources)
|
|
|
* OSSR
|
|
|
* we can build ossr records that have docker recipes using gitlab in2p3 resources
|
|
|
* Issues:
|
|
|
* lot of resources?
|
|
|
* build trigger?
|
|
|
* nightly? need to find a way not to rebuild every night software that has not changed. We can compare the container metadata version and the record one
|
|
|
|
|
|
|
|
|
## where should we gather docker recipes?
|
|
|
|
|
|
centralized git repository vs OSSR
|
|
|
|
|
|
| | Advantages | Drawbacks |
|
|
|
|---|---|---|
|
|
|
| git repository | - pull requests to add env // - continuous integration to build and test the recipe | - gitlab in2p3: accounts and access // - not all OSSR advantages |
|
|
|
| OSSR | - versioned, archived, citable, discoverable // - same metadata schema as other OSSR entries // - many sources (can be managed on whatever platform, be part of several communities...) | - curation process? only one curator at the moment | |
|
|
\ No newline at end of file |