-
Notifications
You must be signed in to change notification settings - Fork 99
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
Mount entire bundle.json
as a file at /var/run/cnab/bundle.json
#144
Comments
Yes, I think this is a great idea. I can't see any downside. In particular, this approach would solve #143 by allowing invocation images to see custom extensions. It would also simplify the runtime by avoiding it having to treat several pieces of |
Agreed! |
cc @silvin-lubecki, we need to track this for docker-app (it will change the way we need to extract the image map in the run tool). |
@youreddy You are working on a PR to fix this issue, so I took the liberty of assigning this issue to you. Please unassign if that's not appropriate. |
* Add bundle.json file to invocation image - Addresses issue #144 * Update 100-CNAB.md Co-Authored-By: Glyn Normington <[email protected]> * Update 100-CNAB.md Co-Authored-By: Glyn Normington <[email protected]>
Closed by #196 |
- Addresses issue cnabio#144
In the first few drafts of the CNAB spec, the
bundle.json
was accessible inside of the invocation image (as part of the building process, it was copied in). We removed that when we lowered the requirements for building a bundle.Now, there are several different pieces of the
bundle.json
that are interesting to authors of invocation images. Should we just require that thebundle.json
be mounted at a fixed location (/var/run/cnab/bundle.json
, for example)?The text was updated successfully, but these errors were encountered: