You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@submarine.apache.org by GitBox <gi...@apache.org> on 2020/06/22 09:42:41 UTC

[GitHub] [submarine] tangzhankun edited a comment on pull request #299: SUBMARINE-507. Submarine Environment Management

tangzhankun edited a comment on pull request #299:
URL: https://github.com/apache/submarine/pull/299#issuecomment-647406373


   @manirajv06 We're almost ready to ship 0.4.0 release. If we remove the "image" field after this PR and only support a "name" in the `environment`. It will break the API.
   Another reason I want to keep it is that there might be the use case that the user doesn't want to register an environment beforehand.
   He just wants to quickly try the application with one ready image which might be built by someone else. He even doesn't want to know what's installed in it. Once he runs an experiment with the image successfully, he might consider registering it without any conda spec.
   If we don't support this, it seems not very flexible to me.
   ```
   environment: {
   image:...
   }
   ```
   
   BTW, do we support just register a docker image as an environment without kernel spec?
   
   {
     "name": "my-submarine-env",
     "dockerImage" : "someone shared based image",
   }


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org