2 years ago
Hello! I'm having trouble deploying keydb with a volume. It keeps giving me an error saying 'Permission denied /volume/path'. I tried setting RAILWAY_RUN_UID and checked the current user (which turned out to be root), but keydb still throws a permissions error. I also checked with ls -l / and confirmed that the volume exists. I even tried renaming it (changing volume path), but nothing worked. Can someone please help me fix this?
Dockerfile:
24 Replies
2 years ago
what did you set RAILWAY_RUN_UID to?
I've spent an hour searching for a solution, checking KeyDB docs, their Docker build images, everything. I'm feeling pretty hopeless about it. If you can manage to solve this issue, it would be wonderful.
2 years ago
where are you mounting the volume?
2 years ago
send the conf file please
2 years ago
are these things configurable via environment variables?
I don't think so. keydb can be configured via a config file or parameters passed to its executable as stated by their docs.
2 years ago
cool, will take a crack at this
2 years ago
give this a try -
I made a small adjustment to the start command by adding "--storage-provider flash /volume/path", and it worked perfectly. Thanks a lot! You're awesome! I'm not sure what mistake I made, though. If you have any insights on what went wrong so I can avoid it next time, that would be fantastic.
2 years ago
why flash?
I needed a cheaper alternative to Redis that still uses the Redis protocol. So, I discovered KeyDB on Flash, which saves on costs by limiting RAM usage and storing data on disk.
2 years ago
oh so with flash no data ever gets saved into memory
KeyDB still uses RAM for hot keys, but you can control how much it uses by using the 'maxmemory' option.
2 years ago
what did you set the path for flash to?
2 years ago
/data?
I've changed the path to something else. I don't quite remember the reason. 😅
2 years ago
haha well please don't blame me if you lose data, i tested it as the template deploys and data did persist
2 years ago
no problem!