Hi Team, We are trying to automate the Flyte deployment using CI/CD and what we have noticed is when we run the or flyte workflow in one of env we are getting following error:

RunContainerError: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: \"pyflyte-execute\": executable file not found in $PATH: unknown" logger="UnhandledError"

But when we try to run the same image from local we can see that

pyflyte-execute

is available but when we run in dev server we get error. For ref I have attached our docker file :

FROM <http://dockerhubproxy.schibsted.io/python:3.9.18-slim|dockerhubproxy.schibsted.io/python:3.9.18-slim>

# The installer requires curl (and certificates) to download the release archive
RUN apt-get update && apt-get install -y --no-install-recommends curl ca-certificates

# Download the latest installer
ADD <https://astral.sh/uv/install.sh> /uv-installer.sh
# TODO: Specify a version
#ADD <https://astral.sh/uv/0.5.#/install.sh> /uv-installer.sh

# Run the installer then remove it
RUN sh /uv-installer.sh && rm /uv-installer.sh

# Ensure the installed binary is on the `PATH`
ENV PATH="/root/.local/bin/:$PATH"

COPY /flyte /flyte
COPY /tests /tests

ENV WORKDIR=/app
WORKDIR $WORKDIR
ENV PYTHONPATH="$WORKDIR:$WORKDIR/flyte"

ENV PATH="/app/.venv/bin:$PATH"

COPY pyproject.toml /pyproject.toml
COPY create_config.sh /create_config.sh

COPY .github/scripts /.github/scripts
RUN chmod +x /.github/scripts/build_and_push_image.sh

# Run the shell script to create the config-remote.yaml file with an argument
# dev is the default value. Can be overridden during the build process using --build-arg.
ARG FLYTE_ENVIRONMENT=dev
RUN chmod +x /create_config.sh && /create_config.sh ${FLYTE_ENVIRONMENT}

# Install a specific version of flytectl
ENV FLYTECTL_VERSION=v0.9.2
RUN curl -sLo flytectl_Linux_x86_64.tar.gz <https://github.com/flyteorg/flyte/releases/download/flytectl/${FLYTECTL_VERSION}/flytectl_Linux_x86_64.tar.gz> && \
	tar -xzf flytectl_Linux_x86_64.tar.gz && \
	install flytectl /usr/local/bin/ && \
	# Clean up downloaded and extracted files
	rm -rf flytectl_Linux_x86_64.tar.gz flytectl

RUN uv sync --inexact --no-cache-dir

So can anyone help us on how to address this issue. Your input and help will be much appreciated

it may have to do with the pythonpath. are you sure it's the right path?

We are installing everything using UV so it should be in correct path, we checked the image from local and was able to execute the

pyflyte-execute --help

command from anywhere in the image

where's pyflyte-execute installed? what's the path?

I think that get installed with the flytekit?

yes, but we could work backwards by first understanding where it's being installed.

Ok let me check

that should be okay as pyflyte-execute gets installed with flytekit.

yes looks like :

PATH=/root/.local/bin:/app/.venv/bin:/root/.local/bin/:/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

the same image being used for CI/CD works locally, right?

Yes

Samhita, what command does flyte execute when running the tasks in a pod? Because, we’re able to pyflyte commands when we tests the docker container locally. Is there a specific

ENTRYPOINT

or another command it does? Also, I thought that the containers themselves do not need to have

pyflyte

installed? I’ve tried to search for docs about this, but have not found anything relevant unfortunately.

> what command does flyte execute when running the tasks in a pod? seems like it's `pyflyte-execute`(ref)

We figured out the issue. A bit difficult to explain, but in short terms, there was an issue with how we set the

WORKDIR

in our

Dockerfile

. Yup, we need to upgrade to a higher

flytekit

version, most def 😊 .

Oh thanks for sharing