Closed alexcos20 closed 2 years ago
I also updated a different ticket (https://github.com/oceanprotocol/provider/issues/509) with the info regarding the container-checksums-check
image. It is now available for testing and more container validation is done via provider, before paying for the job. Once the correct data reaches the c2d services, it will use the proper flow (implemented by Alex before he left). I will therefore mark both the provider and op-engine tasks as done. I added ocean.py updates as well, so only the ocean.js and marketplace tasks remain.
we have the following definition of an algo container:
where checksum is the image digest (ie: sh256: xxxx)
For now, anyone can use an empty checksum, and c2d will start node:latest. Once this algo is approved, the algo publisher will update the image on dockethub with malicios code.
Proposal:
See https://docs.docker.com/engine/reference/commandline/pull/#pull-an-image-by-digest-immutable-identifier
Docs updated in https://github.com/oceanprotocol/docs/pull/1032