Hi all, how do we build docker image from orion branch ?

Executing task: docker build --pull --rm -f "Dockerfile" -t myprefect:latest "." <

Sending build context to Docker daemon  101.5MB
Step 1/38 : ARG PYTHON_VERSION=3.8
Step 2/38 : ARG BUILD_PYTHON_VERSION=3.8
Step 3/38 : ARG NODE_VERSION=14
Step 4/38 : FROM node:${NODE_VERSION}-bullseye-slim as ui-builder
14-bullseye-slim: Pulling from library/node
Digest: sha256:f7137af1e34927cb3251a6e091edff4592c49a89422196680a2f087edcbc6e4d
Status: Image is up to date for node:14-bullseye-slim
 ---> e2eb23c871f2
Step 5/38 : WORKDIR /opt/orion-ui
 ---> Using cache
 ---> 74138fe30a86
Step 6/38 : RUN apt-get update &&     apt-get install --no-install-recommends -y         chromium     && apt-get clean && rm -rf /var/lib/apt/lists/*
 ---> Using cache
 ---> 77731060b4e3
Step 7/38 : RUN npm install -g npm@8
 ---> Using cache
 ---> ac23c1b14bea
Step 8/38 : COPY ./orion-ui/package*.json .
When using COPY with more than one source file, the destination must be a directory and end with a /
The terminal process "/usr/bin/bash '-c', 'docker build --pull --rm -f "Dockerfile" -t myprefect:latest "."'" terminated with exit code: 1.

I wouldn't recommend that since the Orion branch assumes running in a dev mode - why do you need that? 2.0b6 is released on dockerhub

Just trying to figure out why running UI from your image works, and UI installed in docker with pip install prefect does not 🙂

Marcin, could you explain why you need to use the raw version in the first place? do you have some custom modifications which don't exist in 2.0b6?

I don't need it yet, Just checking what is doable in case I need it in the future

I see - if you need to extend the functionality of Prefect 2.0 in the future, the easiest way is by: • creating a custom collection https://orion-docs.prefect.io/collections/overview/ • building some other FastAPI service to communicate with 2.0 backend

ok, thank you, I will read this