Docker/Synology: Issue with Redis after Update from 1.13.3 to 1.18 (Folder Permission Issue) solved

Please fill in the questionnaire below.

Technical Help Questionnaire

Have you read and followed the instructions at:
Answer: Yes

Self-Hosted Installation and Setup Questions

Docker Container on Synology DSM 6

How have you self-hosted Baserow.

What are the specs of the service or server you are using to host Baserow.

DS218+ with 8GBRAM

Which version of Baserow are you using.

1.18

How have you configured your self-hosted installation?

{
“cap_add” : null,
“cap_drop” : null,
“cmd” : “start”,
“cpu_priority” : 50,
“devices” : null,
“enable_publish_all_ports” : false,
“enable_restart_policy” : false,
“enabled” : true,
“entrypoint_default” : “/baserow.sh”,
“env_variables” : [
{
“key” : “BASEROW_BACKEND_DEBUG”,
“value” : “on”
},
{
“key” : “BASEROW_BACKEND_LOG_LEVEL”,
“value” : “DEBUG”
},
{
“key” : “PATH”,
“value” : “/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin”
},
{
“key” : “UID”,
“value” : “9999”
},
{
“key” : “GID”,
“value” : “9999”
},
{
“key” : “DOCKER_USER”,
“value” : “baserow_docker_user”
},
{
“key” : “DATA_DIR”,
“value” : “/baserow/data”
},
{
“key” : “BASEROW_PLUGIN_DIR”,
“value” : “/baserow/data/plugins”
},
{
“key” : “POSTGRES_VERSION”,
“value” : “11”
},
{
“key” : “POSTGRES_LOCATION”,
“value” : “/etc/postgresql/11/main”
},
{
“key” : “BASEROW_IMAGE_TYPE”,
“value” : “all-in-one”
},
{
“key” : “BASEROW_PUBLIC_URL”,
“value” : “/XXXXXX”
},
{
“key” : “BASEROW_EXTRA_ALLOWED_HOSTS”,
“value” : “//YYYYYYY”
},
{
“key” : “BASEROW_WEBHOOKS_ALLOW_PRIVATE_ADDRESS”,
“value” : “true”
}
],
“exporting” : false,
“id” : “2c602d43fec586ab097eb309bf83dea363653865d7f91e9dc9239607b6510dee”,
“image” : “baserow/baserow:1.18.0”,
“is_ddsm” : false,
“is_package” : false,
“links” : [],
“memory_limit” : 0,
“name” : “baserow_1_18”,
“network” : [
{
“driver” : “bridge”,
“name” : “bridge”
}
],
“network_mode” : “bridge”,
“port_bindings” : [
{
“container_port” : 80,
“host_port” : 32831,
“type” : “tcp”
}
],
“privileged” : false,
“shortcut” : {
“enable_shortcut” : false
},
“use_host_network” : false,
“volume_bindings” : [
{
“host_volume_file” : “/docker_SSD/Baserow”,
“mount_point” : “/baserow/data”,
“type” : “rw”
}
]
}

What commands if any did you use to start your Baserow server?

none

Describe the problem

I m getting the following Error on container startup after switching from container 1.13.3 to 1.18

[REDIS][2023-08-06 21:55:11] 167:C 06 Aug 2023 21:55:11.030 # Can’t chdir to ‘/baserow/data/redis’: Permission denied stdout

2023-08-06 21:55:18,934 INFO gave up: redis entered FATAL state, too many start retries too quickly
Baserow was stopped or one of it’s services crashed, see the logs above for more details.

[BACKEND][2023-08-06 21:55:27] redis.exceptions.ConnectionError: Error 99 connecting to localhost:6379. Cannot assign requested address. stdout

[EXPORT_WORKER][2023-08-06 21:55:28] [2023-08-06 21:55:28,689: ERROR/MainProcess] consumer: Cannot connect to redis://:**@localhost:6379/0: Error 99 connecting to localhost:6379. Cannot assign requested address… stdout

Describe, step by step, how to reproduce the error or problem you are encountering.


Provide screenshots or include share links showing:

Folder Permissions and Owner

drwxr-xr-x 1 9999 9999 0 Dec 24 2022 backups

drwxr-xr-x 1 9999 9999 12 Dec 24 2022 caddy

drwxr-xr-x 1 9999 9999 0 Dec 24 2022 env

drwxr-xr-x 1 9999 9999 76 Jan 16 2023 media

drwxr-xr-x 1 9999 9999 0 Aug 6 23:11 plugins

drwx------ 1 102 103 438 Aug 6 23:55 postgres

drwxr-xr-x 1 101 102 0 Dec 24 2022 redis

Please attach full logs from all of Baserow’s services

cant upload the full log as it is too long (max 32000 characters)

I have absolutely no idea what could be wrong and why Redis doesn’t have permission for the folder. Is it correct that Redis has the UID and GID 101:102?

I managed to get it up and running.
I added permissions for Everyone in the parent Baserow folder. The folder owner is 9999:9999, and it seems that the Redis worker with 101:102 didn’t have write access to the redis folder despite being the owner and having the appropriate permissions set. I’ll look into how to resolve this in the future. I don’t like this solution but its working for the moment. If anyone has an idea on how to properly handle this on Synology, please feel free to share.

I don’t think it was an error caused by the update, rather, I accidentally broke it myself while adjusting the permissions at the top-level folder level without realizing it.

BR

Hey @baserow_bln,
thanks for reaching out!
I am glad that you managed to solve the problem.
It seems it is related to DSM, rather than to Baserow.