-
Notifications
You must be signed in to change notification settings - Fork 561
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
Labels and extension meta data in containers #108
Comments
Some additional discussion can be found here: |
I second Solomon 1 in feeling like this is a useful feature, but .
|
@wking FYI, we have decided to use the mailing list for discussion of features that don't exist yet. |
On Tue, Aug 11, 2015 at 03:44:07PM -0700, Brandon Philips wrote:
Right, sorry. It may take me a few iterations to break my fingers ;).
|
This thread came from an issue that is still open [1], so I'm tagging it. My personal feeling is still "this is out-of-scope, use an orthogonal spec and load it in as arbitrary bundle content [2]" [3]. But the issue is still alive and fluxy, and I was just talking about it with Vincent in #opencontainers on 2015-12-18. [1]: opencontainers/runtime-spec#108 [2]: Message-ID: <[email protected]> Subject: Dropping the rootfs requirement and restoring arbitrary bundle content Date: Wed, 26 Aug 2015 12:54:47 -0700
I would like to discuss ability to attach application-specific meta data to container images. Here are a couple of examples that come to mind:
For example, app container spec adresses this use-case by introducing labels:
After trying to use labels in practice, I can say that ACI's labels have the following limitations:
The useful part about labels is namespaces, that helps to identify the purpose of meta data and avoid collisions.
It would be very helpful to include the mechanism of adding meta data to the open container images that addresses some of the limitations listed above.
The text was updated successfully, but these errors were encountered: