Allan Sene08/11/2022, 6:46 PM
(or other ones) image to use a custom one? I know that there is a property
in the orchest-controller, but I'm not sure how is the best way to change this value.
Navid H08/12/2022, 6:53 AM
option in the
to specify the registry where you store your custom images. For example, when not specifying it it will default to DockerHub (
) and use our images. This way you can host the images that you want to use in Orchest. To make sure the in-app updating still works your version tags need to follow CalVer (given that we enforce it in the orchest-cli and call it when updating through the orchest-api). When looking to extend Orchest it is good to be aware of the fact that the Orchest product depends on some external endpoints for some functionality. For example, to incorporate examples into the product it will pull the applicable information from https://github.com/orchest/orchest-examples, and to show a update dialog (indicating that a new version is available) it will also poll from an external endpoint (so you would have to make sure this endpoint returns a version of your choosing). Of course you can change, in the code, the endpoints that are called (and how). --- For the case of development, you just need to make sure that your images are on the nodes under the
etc. names so that the
will resort to using your images instead of pulling them from DockerHub (or your custom registry). For this, we use the
script (as you can read in the development docs). I hope that answers your question. If it doesn't or if it doesn't cover your use case, then please feel free to reach out again 😉
Allan Sene08/12/2022, 9:54 PM
feature as well, right? This way, we can keep track about the updates, making sure that our changes does not conflict with the main repo
Alexsander Pereira08/16/2022, 1:57 PM
I saw that you suggested modifying the services/orchest-api/app/app/core/environment_image_builds.py file in the orchest-api to pull my custom images.Please be aware that these changes only apply to Environment base images, not to changes for e.g. the
or other Orchest services.
But how do I register the custom orchest-api image in EKS?This is done by pushing all the images to another registry (other than DockerHub because that is where we host our images) and specifying the
) in the CR Object to point to that registry. Then the
should pull the images from the registry you configured, containing your custom images. Does that answer your question?
Alexsander Pereira08/16/2022, 2:36 PM
apiVersion: <http://orchest.io/v1alpha1|orchest.io/v1alpha1> kind: OrchestCluster metadata: name: cluster-1 namespace: orchest spec: singleNode: true
apiVersion: <http://orchest.io/v1alpha1|orchest.io/v1alpha1> kind: OrchestCluster metadata: name: cluster-1 namespace: orchest spec: singleNode: true orchest: registry: ...
Isn't there a way to change just the image of the orchest-webserver?At this point in time there is not. It would require some changes in the
to make this possible. For your information, we don't allow changing only the image for the
(and other services) to ensure that Orchest is in a consistent state and we know we can update to a new version. Of course we can make some changes to make it possible to specify a custom image. Could you share a little more about your use case and what you are looking to achieve? E.g. just specifying
as the image to be used for the
Alexsander Pereira08/16/2022, 2:47 PM
Navid H08/16/2022, 2:49 PM
Alexsander Pereira08/16/2022, 3:12 PM
apiVersion: <http://orchest.io/v1alpha1|orchest.io/v1alpha1> kind: OrchestCluster metadata: name: cluster-1 namespace: orchest spec: singleNode: true orchest: orchestWebServer: image: alexsanderdadosfera/orchest-webserver:latest
The Spec file lets you define an image, shouldn't that work?This doesn't work currently to prevent users from "breaking things". Given that we can no longer ensure that Orchest works correctly when specifying a custom image. Nevertheless, @Navid H and I have just had a discussion and we can make it possible to specify a custom image (just like you did above) 🙌 . Be aware that this would result in updating to no longer work and you would have to manually update the CR Object defining your
in case you want to deploy another Orchest version with your custom changes. Reason being is that we can only update an
that uses only "Orchest owned" images, thus if you specify a custom image then updating will no longer work. In summary, we will do a new Orchest release (hopefully today or tomorrow) that allows you to specify a custom image in the CR
at the cost of losing the ability to update from within the application (or using the
) and having to manually update the
Does that work for you @Alexsander Pereira?
Alexsander Pereira08/16/2022, 5:47 PM
Alexsander Pereira08/18/2022, 2:13 PM
Navid H08/18/2022, 2:17 PM
Alexsander Pereira08/18/2022, 2:23 PM
Allan Sene08/18/2022, 8:20 PM
Alexsander Pereira08/19/2022, 7:03 PM