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
since about two weeks, we are trying to use our own custom image within this framework. We therefore updated the
.pipelines/diabetes_regression-ci.yml
but found out, that it does not influence the environment which is being used within ml.azure.com at all.
Next we updated
MLOpsPython/environment_setup/Dockerfile
diabetes_regression/ci_dependencies.yml
and noticed that the environment setup is only done once upon setup of the whole environment.
Is there a possibility to always use a new image created within the CI step? It seems kind of strange that within the CI step no image is produced.
The text was updated successfully, but these errors were encountered:
We are actually using the environment from a Docker image. We therefore changed the environment to load a Docker image (including Parent image, username and password) within the UI. It is working nicely and also seems to automatically detect if the underlying Docker image has changed. On the other hand we were unable to setup a Docker connection correctly within the manage_environemnt.py to load a Docker image from an external repository.
Hello,
since about two weeks, we are trying to use our own custom image within this framework. We therefore updated the
.pipelines/diabetes_regression-ci.yml
but found out, that it does not influence the environment which is being used within ml.azure.com at all.
Next we updated
MLOpsPython/environment_setup/Dockerfile
diabetes_regression/ci_dependencies.yml
and noticed that the environment setup is only done once upon setup of the whole environment.
Is there a possibility to always use a new image created within the CI step? It seems kind of strange that within the CI step no image is produced.
The text was updated successfully, but these errors were encountered: