Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

I can't deploy my application on Cloud Run, but the data is still processed.

Hello,

I have created an image and deployed it on Artefact Registry. I've already used this image with Argo Workflow and it works very well. To launch this image I run the command "poetry run process dev ing001".

I then tried to launch this image via Cloud Run.

However, I get the following error:

"Revision ' ' is not ready and cannot serve traffic. The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable."

This is my Dockerfile :

 

FROM python:3.10-bullseye

WORKDIR /opt

RUN apt-get update && apt-get install -y curl && \
    apt-get clean && rm -rf /var/lib/apt/lists/*

ENV POETRY_VERSION=1.8.3
RUN curl -sSL https://install.python-poetry.org | python3 - --version $POETRY_VERSION

ENV PATH="/root/.local/bin:$PATH"

COPY poetry.lock pyproject.toml /opt/

RUN poetry install --no-root --no-interaction

WORKDIR /opt
COPY src src

RUN poetry install --no-interaction

RUN poetry run pylint **/*.py

EXPOSE 8080

CMD ["poetry", "run", "process", "dev", "ing001"]

 

My application is a python application that uses click and poetry. The application's input is the :

 

import click

from source.processing.principal_processor import PrincipalProcessor


@click.command()
@click.argument("env")
@click.argument("source_name")
def cli(env, source_name):
    PrincipalProcessor(env, source_name).process()

 

Furthermore, the purpose of my application is to move csv data from a bucket to bigquery using pandas and pandas_gbq.

And despite this error, the data is still transferred to bigquery.

I try to follow this link https://cloud.google.com/run/docs/troubleshooting but problem still progress

Can you help me please ?

0 1 391
1 REPLY 1

From my experience, this error could mean a bunch of different things. The best way to find out what the actual error is is to go the the logs tab and search for the last message before the "yellow warning sign", that's usually what caused the error. Hopefully, this helps you streamline your debugging process.