We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker Compose version v2.15.1 kvrocks version 2.8.0.
when using the following docker-compose configs
kvrocks: image: apache/kvrocks:latest ports: - "6366:6366" volumes: - ./kvrocks/conf/kvrocks.conf:/etc/kvrocks/conf/kvrocks.conf entrypoint: ["kvrocks", "-c", "/etc/kvrocks/conf/kvrocks.conf"]
and the kvrocks.conf file:
dir /tmp/kvrocks # General #daemonize yes port 6366 bind 0.0.0.0
I expected the service to start...normally and I am able to connect with redis-cli -p 6366
⠿ Container microservices-kvrocks-1 Created 0.0s Attaching to microservices-kvrocks-1 microservices-kvrocks-1 | E20240614 15:41:22.642987 1 main.cc:180] Failed to start server: rename file encounter error: Resource busy
A quick solution is to mount the directory which contains the configuration file as follows:
volumes: - ./kvrocks/conf:/etc/kvrocks/conf
The text was updated successfully, but these errors were encountered:
@alija83 Thanks for your report. This issue should involve two problems:
/var/lib/kvrocks
Sorry, something went wrong.
@alija83 Feel free to reopen if you have any further questions.
No branches or pull requests
Search before asking
Version
Docker Compose version v2.15.1
kvrocks version 2.8.0.
Minimal reproduce step
when using the following docker-compose configs
and the kvrocks.conf file:
What did you expect to see?
I expected the service to start...normally and I am able to connect with redis-cli -p 6366
What did you see instead?
⠿ Container microservices-kvrocks-1 Created 0.0s
Attaching to microservices-kvrocks-1
microservices-kvrocks-1 | E20240614 15:41:22.642987 1 main.cc:180] Failed to start server: rename file encounter error: Resource busy
Anything Else?
A quick solution is to mount the directory which contains the configuration file as follows:
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: