-
Notifications
You must be signed in to change notification settings - Fork 541
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
Is PORTS field neccessary for oci specs? #178
Comments
I think this job should be done by upper program such as Docker, Hyper etc. upper program should manage network itself. |
That is a higher level. At best there might could be interface level requests, but not port level. |
On Thu, Mar 17, 2016 at 08:29:13AM -0700, Matthias Lübken wrote:
Networking is out-of-scope for the OCI runtime spec. For more
|
@wking thanks for the pointers. But I'm not so much into the topic that I would feel ready for writing a wiki entry. I do understand the tension not introducing more areas into this spec like networking. At the same time I feel that declaring what ports a container is listening on would be quite beneficial. And this is independent of the underlying network solution. @vbatts what do you mean by "interface level" in
|
On Thu, Mar 24, 2016 at 05:54:31AM -0700, Matthias Lübken wrote:
The runtime won't care about them, but they may be interesting to { in your config.json, although we'd need to land an opaque type 1 to { with the bundled Go types. |
The container will listen on the specified network ports at runtime for the purpose of interconnecting, as a result, I think exposed port is important for the container runtime. Is it neccessary to add PORTS field for the specs. Maybe it is appropriate to add Port struct in runtime_config.go.
The text was updated successfully, but these errors were encountered: