Hi team, any hints on how to run flyteconsole in d...
# ask-the-community
v
Hi team, any hints on how to run flyteconsole in development mode? i tried changing the dockerfile to this but i get errors:
Copy code
=> ERROR [builder 6/6] RUN :   --mount=type=cache,target=/root/.yarn   && mkdir /app   && cp -R ./website/console/dist/* /app                                                                                                                  0.2s
------
 > [builder 6/6] RUN :   --mount=type=cache,target=/root/.yarn   && mkdir /app   && cp -R ./website/console/dist/* /app:
#14 0.189 cp: cannot stat './website/console/dist/*': No such file or directory
any help would be appreciated
Copy code
# syntax=docker/dockerfile:experimental

FROM node:21.6.0 as builder
LABEL org.opencontainers.image.source <https://github.com/flyteorg/flyteconsole>

ARG TARGETARCH
ENV npm_config_target_arch "${TARGETARCH}"
ENV npm_config_target_platform linux
ENV npm_config_target_libc glibc

WORKDIR /my-project/
COPY . /my-project/

# install production dependencies
RUN : \
  --mount=type=cache,target=/root/.yarn \
  && yarn workspaces focus --all

# build console web app
RUN : \
  --mount=type=cache,target=/root/.yarn \
  && BASE_URL=/console yarn workspace @clients/console run build

# copy console build to /app
RUN : \
  --mount=type=cache,target=/root/.yarn \
  && mkdir /app \
  && cp -R ./website/console/dist/* /app

FROM <http://gcr.io/distroless/nodejs|gcr.io/distroless/nodejs>
LABEL org.opencontainers.image.source <https://github.com/flyteorg/flyteconsole>

COPY --from=builder /app app
WORKDIR /app
ENV NODE_ENV=development BASE_URL=/console PORT=8080
EXPOSE 8080

USER 1000

CMD ["server.js"]
d
@Vinayak could you verify if the build command is correctly populating the output in the
./website/console/dist/
folder?
v
yes, the build and creation of the dist folder works correctly. when i run
build
instead of
build:prod
(which is committed in oss), the command seems to always be listening and doesn't terminate:
Copy code
server (webpack 5.90.3) compiled with 1 warning in 21356 ms
I wonder if that is what causes this issue