https://bugzilla.redhat.com/show_bug.cgi?id=1444729
--- Comment #2 from Tomas Repik <trepik(a)redhat.com> ---
(In reply to Juraci Paixão Kröhling from comment #1)
The line 8 of `run-cassandra` looks suspicious to me and could
explain the
behavior above, as it seems that it's starting Cassandra and not stopping it.
What I'm actually doing is running cassandra to get the IP address of the
machine to store it as a SEED in the config (cassandra.yaml) file. The first
run of cassandra always fails, because there are no seeds set in config file,
and thus does not have to be stopped (no need for Ctrl+C). The first run is
done in silence so you don't see any output in terminal. Once the first run is
done and the config file is filled with the obtained seed value, the server
starts normally.
1) wouldn't it be better to use `FROM fedora:rawhide` instead of
`FROM
registry.fedoraproject.org/fedora:rawhide`?
guidelines say that registry is mandatory therefore using it that way [1]
2) CONTAINER_SCRIPTS_PATH is exported, but the referred path
doesn't exist:
Yes you're right the concept is taken from other database containers we have
and so far in cassandra we don't have any use for it. I will skip it if don't
use it.
3) OpenShift assigns a random UID to the process within the
container, so,
the user that ends up running the process might not have enough permissions.
I had the loosening of permissions in the dockerfile and I did not know the
purpose for it so I commented it out. For Fedora it is not necessary for
openshift we can definitely include it.
Thank you very much for feedback!
[1]
https://fedoraproject.org/wiki/Container:Guidelines#FROM
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug
https://bugzilla.redhat.com/token.cgi?t=0PaZ60bZ1L&a=cc_unsubscribe