Redis Deployment Error - missing tag
Anonymous
HOBBYOP

3 months ago

Hi all, can you help? Im trying to deploy a redis image as part of an Evolution API template and when i deply the template i hit this Redis error

"this image does not have a 7.2.5 tag"

Has anyone been able to solve this?

Attachments

Solved$10 Bounty

13 Replies

dardameiz
PRO

3 months ago

Hello

The tag 7.2.5 does not exist in the official Redis Docker repository. This is why the deployment fails. Try to do the following:

1. Find the image: line in your template's configuration.

2. Change redis:7.2.5 to a guaranteed, existing tag:

- redis:7.2 (Pulls the latest stable 7.2 release, which is currently 7.2.12 or similar).

• redis:latest (Pulls the newest stable Redis version).

Let me know if it worked


Anonymous
HOBBYOP

3 months ago

Ok thanks, it made it through into deployment then took 26 minutes to try and create the container before i got a failure
The logs show

https://railway.com/project/f7777890-12f2-402b-bb66-bf175c0c8acf?environmentId=86333231-e303-42f5-a1e9-5efd933b5df0


dardameiz
PRO

3 months ago

Its failing due to the container trying to see if redis healthcheck is ok but railway can never see this and it gets timed out. Can you check if there is anything in redis - settings - healthcheck path? If yes you could delete it and try to redeploy. Can you show me if you have redis set up in redis.conf?


Anonymous
HOBBYOP

3 months ago

Healthceck path is empty and i cant find redis.conf

Here are the config screenshots


dardameiz
PRO

3 months ago

ok I see, you are using bitnami. If you need to use bitnami, then add to the variables this:

ALLOW_EMPTY_PASSWORD=“yes”

If you no need to use, just change bitnami/redis:7.2 to only redis:7.2


dardameiz
PRO

3 months ago

Bitnami requires password, or you can use password (recommended)

REDIS_PASSWORD=“your-password”


Anonymous
HOBBYOP

3 months ago

Great, i now have one final issue with my setup. The Bucket node failed to deploy due to healthcheck issues with minio

Attachments


Anonymous
HOBBYOP

3 months ago

Here are the logs

Attachments


Anonymous
HOBBYOP

3 months ago

Here is the config


dardameiz
PRO

3 months ago

  1. you might need to add PORT to the custom start command, try this:

    /bin/sh -c "exec minio server /data --address [::]:$PORT --console-address [::]:$MINIO_CONSOLE_PORT"

here we are adding /data as well for the storage directory

2. then you would want to add to the environmental variables these:

PORT - Railway will auto-assign this for the API

MINIO_CONSOLE_PORT - Set to something like 9001 (this is important)

MINIO_ROOT_USER - Your admin username

MINIO_ROOT_PASSWORD - Your admin password

  1. in the healthcheck path you have /minio/health/ready

    try to change it to /minio/health/live

let me know if this helped


Anonymous
HOBBYOP

3 months ago

Thanks, giving it a try


Anonymous
HOBBYOP

3 months ago

Yes that was successful amazing thanks


dardameiz
PRO

3 months ago

amazing! slightly_smiling_face emoji


Status changed to Solved brody 3 months ago


Loading...