You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
org.opencontainers.image.source URL to get source code for building the image (string)
I was wondering how I should set this for multiple images that are all sharing the same git repository (a NodeJS monorepo):
a) All images point to the root of the git repo
b) All images specify the specific sub-folder path within the link so that people who click on it are taken there directly and won't have to look for it manually (we have a repo with 10+ Dockerfiles that aren't trivial to find unless you are already familiar with the directory structure of mono-repositories in general)
To me, option b) sounds better because it's more convenient to the user, but I wanted to double check if this is what the spec authors would've expected and also if there would be some interest in adding some additional clarifications to the spec regarding the preferred/recommended approach (if there is one)
The give more context, here is a (partial) list of container image definitions in the Hyperledger Cactus repo that I'm a maintainer of:
The text was updated successfully, but these errors were encountered:
From the spec:
I was wondering how I should set this for multiple images that are all sharing the same git repository (a NodeJS monorepo):
a) All images point to the root of the git repo
b) All images specify the specific sub-folder path within the link so that people who click on it are taken there directly and won't have to look for it manually (we have a repo with 10+ Dockerfiles that aren't trivial to find unless you are already familiar with the directory structure of mono-repositories in general)
To me, option b) sounds better because it's more convenient to the user, but I wanted to double check if this is what the spec authors would've expected and also if there would be some interest in adding some additional clarifications to the spec regarding the preferred/recommended approach (if there is one)
The give more context, here is a (partial) list of container image definitions in the Hyperledger Cactus repo that I'm a maintainer of:
The text was updated successfully, but these errors were encountered: