GitHub
08/10/2022, 12:41 PMAllan Sene
08/11/2022, 6:46 PMorchest-webserver
(or other ones) image to use a custom one?
I know that there is a property orchestWebServer
in the orchest-controller, but I'm not sure how is the best way to change this value.Alexsander Pereira
08/11/2022, 8:29 PMapiVersion: <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
Alexsander Pereira
08/11/2022, 8:29 PMVolker Lorrmann
08/11/2022, 10:18 PMjuanlu
08/17/2022, 9:54 AMv2022.03.6
). the good news is that you can now migrate it to the latest version! To perform the migration, go to your Cloud dashboard, click on the "..." three dots to the right of the instance, and select "Migrate to the latest version".
After the migration, the upgrades will continue working as usual and you will be able to enjoy the new File Manager, the improved Pipeline Editor view, the context menu, and much more! check out your Cloud Dashboard ๐ฎrchest:Nikhil Reddy
08/18/2022, 8:10 AMNikhil Reddy
08/18/2022, 8:10 AMNikhil Reddy
08/18/2022, 8:36 AMGitHub
08/19/2022, 9:38 AMAlex Gittings
08/23/2022, 10:57 AMjuanlu
08/23/2022, 3:43 PMSebastiรกn Barrios Slight
08/23/2022, 7:40 PMRobert Sun
08/24/2022, 9:08 AMRobert Sun
08/24/2022, 10:12 PMStarting worker...
Starting image build.............
Copying context.....There was a problem building the image. The building script had a non 0 exit code, build failed.
The logs from the image-build-task container are :
init time="2022-08-24T22:11:21.922Z" level=info msg="Starting Workflow Executor" executorType โ
โ init time="2022-08-24T22:11:21.924Z" level=info msg="Creating a emissary executor" โ
โ init time="2022-08-24T22:11:21.924Z" level=info msg="Executor initialized" deadline="0001-01- โ
โ init time="2022-08-24T22:11:21.952Z" level=info msg="Start loading input artifacts..." โ
โ init time="2022-08-24T22:11:21.952Z" level=info msg="Alloc=4910 TotalAlloc=9295 Sys=74065 Num โ
โ main STEP 1/6: FROM <http://docker.io/orchest/base-kernel-py:v2022.08.8|docker.io/orchest/base-kernel-py:v2022.08.8> โ
โ main STEP 2/6: LABEL _orchest_project_uuid=f5f62dca-b5ad-40e3-a522-a29220d966f2 โ
โ main --> Using cache 438dc990cbb2581f4d42e4c852b0630acc0ee6c016865ea762e37eb332af237b โ
โ main --> 438dc990cbb โ
โ main STEP 3/6: LABEL _orchest_environment_uuid=1bfd8c08-5b24-4a66-9a84-a50dd5e16652 โ
โ main --> Using cache 823aad6fe66e4bcfba5da3946e8acae6a8eb36df47922c7eb49b46cc7461e816 โ
โ main --> 823aad6fe66 โ
โ main STEP 4/6: WORKDIR /project-dir โ
โ main --> Using cache 1593801dc92911eadd946ad8cf53027fe64a7d893896a251bd70307b6f49bd0a โ
โ main --> 1593801dc92 โ
โ main STEP 5/6: COPY . . โ
โ main error committing container for step {Env:[PATH=/opt/conda/bin:/usr/local/sbin:/usr/local โ
โ main Error: exit status 125 โ
โ Stream closed EOF for orchest/image-build-task-4a159dc2-a4b3-4050-816e-976dfbe7858e (init) โ
โ Stream closed EOF for orchest/image-build-task-4a159dc2-a4b3-4050-816e-976dfbe7858e (main) โ
โ wait time="2022-08-24T22:11:22.437Z" level=info msg="Starting Workflow Executor" executorType โ
โ wait time="2022-08-24T22:11:22.440Z" level=info msg="Creating a emissary executor" โ
โ wait time="2022-08-24T22:11:22.440Z" level=info msg="Executor initialized" deadline="0001-01- โ
โ wait time="2022-08-24T22:11:22.440Z" level=info msg="Starting deadline monitor" โ
โ wait time="2022-08-24T22:11:26.440Z" level=info msg="Main container completed" โ
โ wait time="2022-08-24T22:11:26.441Z" level=info msg="No Script output reference in workflow. โ
โ wait time="2022-08-24T22:11:26.441Z" level=info msg="No output parameters" โ
โ wait time="2022-08-24T22:11:26.441Z" level=info msg="No output artifacts" โ
โ wait time="2022-08-24T22:11:26.441Z" level=info msg="Killing sidecars []" โ
โ wait time="2022-08-24T22:11:26.441Z" level=info msg="Alloc=4742 TotalAlloc=9333 Sys=74065 Num โ
โ Stream closed EOF for orchest/image-build-task-4a159dc2-a4b3-4050-816e-976dfbe7858e (wait)
Has anyone run into this? Any help or clue as to where the configuration is wrong?Tech Account
08/25/2022, 4:24 PMTech Account
08/25/2022, 4:25 PMTech Account
08/25/2022, 4:25 PMGitHub
08/29/2022, 8:57 AMGitHub
08/29/2022, 12:39 PMAlexsander Pereira
08/29/2022, 1:26 PMGitHub
08/29/2022, 3:09 PMRick Lamers
08/30/2022, 12:14 PMNelson Silva
09/01/2022, 1:20 PMjuanlu
09/01/2022, 4:32 PMKrishna Sangeeth KS
09/04/2022, 12:43 PMKrishna Sangeeth KS
09/04/2022, 12:50 PMorchest install
option and installation was clean.
I am trying to run the sample pipeline from global-key-value
. It fails for some reason and i couldn't find any logs associated with it.
In the k8s namespace, i briefly saw this pod coming up and then i think it got cleaned up. Any pointers on how to debug this further ?
pipeline-run-task-b9ce091c-baad-4477-915a-77f46dc4c192-12230460 0/2 Init:1/2 0 18s
juanlu
09/06/2022, 8:07 AMAlexsander Pereira
09/06/2022, 3:44 PMArseny Sokolov
09/07/2022, 11:22 AMArseny Sokolov
09/07/2022, 11:22 AM