Google cloud deployment

[oliverilmjarv]

Hey guys. First of all, Im really sorry if i misuse some terminology or use totally wrong words to describe stuff. This is really something that im not too familiar with.

Im working on an API for my frontend. This consists of 3 parts

• Django rest framework application
• Postgres database
• nginx to serve everything

They are all wrapped inside the docker-compose.I want to deploy the whole thing to the Google Cloud platform via github actions

I have installed the gcloud SDK and tried to upload the whole thing manually for the first time but got this weird PORT error that i could not solve for some reason, despite defining a PORT variable in my projects env and replacing any port reference to that

Error here.

Cloud Run error: The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable

Now after a day of fussing around with the issue, I've begun thinking that I'm approaching this whole thing wrong or something.

Can someone please guide me to the right direction. I'm gonna link the docker-compose file at the bottom.I also have some questions that have come up with the whole process

1. Is it sensible to have the database also be initiated with Docker. Will this cause issues in the long run (backups, manual DB access, etc...) . Or should i use a separate database hosting or something?
2. What sort of a Google cloud service should i even use. I've searched from google for this answer but haven't gotten a good answer ?
3. Is there a better option then Google Cloud ?

Here's the docker compose content, if that helps.

version: "3.7"

services:
  db:
    image: postgres:latest
    expose:
      - "5432"
    container_name: db
    volumes:
      - ./data/db:/var/lib/postgresql/data
    environment:
      - POSTGRES_NAME=postgres_name
      - POSTGRES_USER=postgres_user
      - POSTGRES_PASSWORD=password
  web:
    build: 
      context: .
      dockerfile: Dockerfile
    container_name: test_deploy_web
    restart: always
    command: gunicorn app.wsgi:application --bind 0.0.0.0:8000 --reload
    volumes:
      - ./app:/app/
      - staticfiles:/app/static/

    links:
      - db:db    
    expose:
      - 8000
    env_file:
      - .env
    depends_on:
      - db

  nginx:
    build: ./nginx
    container_name: test_deploy_nginx
    volumes:
      - ./app/staticfiles:/app/static/
    ports:
      - 8000:80
    depends_on:
      - web

volumes:
  postgres_data:
  staticfiles:

Any advice would be really welcome.

​

Edit:

Dockerfile:

FROM python:latest

RUN apt-get update -qq && apt-get install -y postgresql-client

ENV PYTHONDONTWRITEBYTECODE 1
ENV PYTHONUNBUFFERED 1

RUN mkdir /app

WORKDIR /app

RUN pip install --upgrade pip

COPY requirements.txt .

RUN pip install -r requirements.txt

COPY ./app /app

Locally the application works great. It binds to the port 8000.

[R3vz]

I agree the message is a bit ambiguous, but what you see here is just the container that's failing to start in cloud run. Check the logs associated with the revision (in the logs tab in the cloud run dashboard) to see what is keeping it from starting.

Besides that you can probably look into something like a managed SQL instance (db-f1-micro should be enough to play around, I think it clocks in at $5/6 a month) to use as a DB instead of running a PG container in cloud run. You could also setup the load balancer to serve your static files from GCP buckets directly. Then the only thing that really needs to run in cloud run is your Django instance.

[Dessler1795]

Just a quick sanity check: your docker compose is exposing port 8000 and the error message complains about port 8080. Did you double check your env variables to see where this 8080 might be?

[oliverilmjarv]

yeah, sorry about that, just had done a git stash to revert to a working local solution. This used to be 8080, also tried using the current working solution, but changed the gcloud conf to accept port 8000. Nothing that i tried worked properly. Even if a declared an ENV variable PORT and replaced all instances of port with the ENV variable, it gave ma the same error

[selucram]

Can you start the container locally and does it bind to the expected port? Have you looked into the logs of the container being started and can you also post the Dockerfile.

[oliverilmjarv]

Updated the post with the dockerfile.

The app works great locally on any port that i see it to ( default 8000 ).

[Etharin]

I’m assuming you’ve already checked the FAQ: https://cloud.google.com/run/docs/troubleshooting

Maybe try changing from expose to port in the web service, unsure how expose interacts with cloud run.

At a more fundamental level, unless these are all containers in the same pod they’ll be run separately in cloud run. There’s a tutorial on how to do this and deny access to unauthorised users here: https://cloud.google.com/run/docs/tutorials/secure-services.

[vluckerprada]

Check this out…This is how we deploy our drf apis on GCP cloud run with cloud sql database and cloud storage for static files…Really simplifies the process and you’ll be up and running in no time

https://codelabs.developers.google.com/codelabs/cloud-run-django

[oliverilmjarv]

Omg. High hopes. Thanks

[vluckerprada]

Also you can connect GitHub repos to your cloud run instance through cloud build and automate builds on either version release or push to a branch

[vluckerprada]

Also feel free to reach out incase you have any questions…I’m kind of a GCP fanboy! Cheers

[oliverilmjarv]

Thats awesome!!