Python error when running "okteto up"

[roncemer]

Followed the instructions here: https://www.okteto.com/blog/develop-django-celery-app-in-kubernetes/

When I ran the "okteto up" command, after selecting the correct Kubernetes context, it throws a Python error about importing Celery.

I'm running okteto against a 3-node K3s cluster. The "kubectl apply -f manifests" command succeeded, and all of the resources are green in the Kubernetes Dashboard. However, once I get the error with "okteto up", the "worker" resources go red in the Kubernetes Dashboard.

Versions:

$ okteto version
okteto version 2.21.0

$ k3s --version
k3s version v1.26.4+k3s1 (8d0255af)
go version go1.19.8

Output of "okteto up" command attached.
out.txt

[roncemer]

Googling the error gives me this: https://stackoverflow.com/questions/74025035/importerror-cannot-import-name-celery-from-celery

The indication seems to be that it's a mistake to name the file celery.py, as that conflicts with the celery package itself.

[roncemer]

One issue is the difference in requirements.txt between this project and the octeto/django:latest Docker image which it uses.

Project:
django==4.2
celery==5.3.1
djangorestframework==3.14.0
psycopg2==2.9.6
redis==4.6.0

octeto/django:latest Docker image:
django==1.11.28
celery==3.1.20
djangorestframework==3.9.4
psycopg2==2.8.4
redis==2.10.5

There is no way the two are compatible. You should build a new Docker image using the same packages as this projetc, and properly tag it with octeto/django:4.2, then push it up to dockerhub, and adjust your image tags to be octeto/django:4.2 instead of octeto/django:latest in the deployment manifests.

This is one of the many reasons why it's VERY BAD practice to use "latest" image tags in deployment manifests.