kvrocks: Docker container exits with code 132 and no output
Search before asking
- I had searched in the issues and found no similar issues.
Version
Ubuntu 20.04.1 LTS \n \l Linux home 5.4.0-122-generic #138-Ubuntu SMP Wed Jun 22 15:00:31 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Docker version 19.03.5, build 633a0ea838
docker image apache/kvrocks:2.2.0
Minimal reproduce step
$ docker run -i --rm apache/kvrocks:2.2.0 $ echo $? 132
What did you expect to see?
- Output logs with the reason why kvrocks exited
- Kvrocks don’t exit but works
What did you see instead?
no logs, no output, just exit 132
Anything Else?
tried tags nightly, 2.1.0 with same bad result. but kvrocks/kvrocks:latest image did output version number and worked until i triggered CTRL-C:
$ docker run -i --rm kvrocks/kvrocks
Version: 2.0.6 @4e5883e9
^C
Are you willing to submit a PR?
- I’m willing to submit a PR!
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 18 (16 by maintainers)
Commits related to this issue
- Fix: Enable portable flag for Docker container builds Fixes issue #1146 — committed to ovaistariq/kvrocks by ovaistariq a year ago
@git-hulk here you go: https://github.com/apache/kvrocks/pull/1602
@git-hulk building the binary with
PORTABLE=1fixes the issue and I no longer see a crash on AMD systems.