Skip to content
New issue

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

kvrocks does not start when customised kvrocks.conf is used #2364

Closed
1 of 2 tasks
alija83 opened this issue Jun 14, 2024 · 2 comments
Closed
1 of 2 tasks

kvrocks does not start when customised kvrocks.conf is used #2364

alija83 opened this issue Jun 14, 2024 · 2 comments
Labels
bug type bug

Comments

@alija83
Copy link

alija83 commented Jun 14, 2024

Search before asking

  • I had searched in the issues and found no similar issues.

Version

Docker Compose version v2.15.1
kvrocks version 2.8.0.

Minimal reproduce step

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

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:

    volumes:
      - ./kvrocks/conf:/etc/kvrocks/conf

Are you willing to submit a PR?

  • I'm willing to submit a PR!
@alija83 alija83 added the bug type bug label Jun 14, 2024
@git-hulk
Copy link
Member

@alija83 Thanks for your report. This issue should involve two problems:

@git-hulk
Copy link
Member

@alija83 Feel free to reopen if you have any further questions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug type bug
Projects
None yet
Development

No branches or pull requests

2 participants