@ancient-wolf-19325 I am unable to build a container if it include

flytekitplugins-pod

. There is no docker error it just hangs repeating the messages

INFO: This is taking longer than usual.
...
Collecting adlfs>=2023.3.0 (from flytekit>=1.3.0b2->flytekitplugins-pod) 
...
239.0 Collecting flytekit>=1.3.0b2 (from flytekitplugins-pod)
239.0   Downloading flytekit-1.13.3-py3-none-any.whl.metadata (5.7 kB)

The issue you're experiencing might be related to the dependencies and the environment in which you're building the container. This can sometimes happen due to network issues, package repository problems, or conflicts between package versions. 1. Check Network and Repository: Ensure that your network connection is stable and that there are no issues with the package repository you're using. Sometimes, switching to a different repository mirror can help. 2. Dependency Conflicts: There might be conflicts between the versions of

flytekit

and

flytekitplugins-pod

. Ensure that all dependencies are compatible with each other. 3. Build Environment: If you're building on a MacBook with an M1 chip, ensure that you're building the image for the correct architecture. You might need to use Docker Buildx to build multi-platform images. 4. Verbose Logging: Enable verbose logging to get more details about where the process is hanging. This can be done by setting the

PIP_VERBOSE

environment variable to

1

. Here is an example Dockerfile snippet to help you troubleshoot:

# Use a base image
FROM python:3.8-slim

# Set environment variables
ENV PIP_NO_CACHE_DIR=1
ENV PIP_VERBOSE=1

# Install dependencies
RUN pip install --upgrade pip
RUN pip install flytekit==1.13.3 flytekitplugins-pod

# Add your application code
COPY . /app
WORKDIR /app

# Install application dependencies
RUN pip install -r requirements.txt

# Command to run your application
CMD ["python", "your_application.py"]

If the issue persists, consider isolating the problem by building a minimal container with just

flytekit

and

flytekitplugins-pod

to see if the problem is with these packages or with other parts of your build process. Would you like more detailed steps or further assistance? Sources: - Flyte GitHub Issue #4985 - Flyte GitHub Issue #4813 - Flyte GitHub Issue #2072 - Flyte Discuss - Workflow execution seems to start but failing with the error - Flyte Discuss - Hi Team I am following the first example to launch a test workflow 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@ancient-wolf-19325 removing boto from the package list fixed it. It was not needed and probably caused a circular dependency or similar

Removing

boto

from the package list likely resolved the issue because

flytekit

and its plugins already handle AWS interactions through

fsspec

and other dependencies, reducing the need for

boto

and avoiding potential conflicts. Would you like more details on managing dependencies in Flyte or any other assistance? Sources: - Flyte GitHub Issue #4418 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

in case anyone ends up here with the same issue 1. upgrade pip 2. use specific library versions in ImageSpec. In my case this was

packages=["flytekitplugins-pod==1.13.4", "boto3==1.33.7"],