You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ ls -lah /elastic_cloud_apps/runner
total 16K
drwxrwxr-x 1 199 199 65 Apr 28 14:36 .
On ubuntu, user ece is well set as owner of /elastic_cloud_apps/runner, but on SLES it shows its uid 199
For bootstrapper docker container, it's well displayed ece and not its uid
Also, the following command does not work:
$ setuser ece whoami
setuser: user ece not found
This does not make sense as ece user is well defined in /etc/passwd
Again, it's all good on ubuntu and on SLES from inside boostrapper container
My guess is that docker have issues with mapping uid/gid between the host and the container. Indeed, the user/group ece does not exists on the host. And so, elastic does not belong to group ece on the host.
Workaround
On the host, create a user and group named ece with uid/gid both 199, and add user elastic to ece group.
Then run ECE installer, and that should work!
The text was updated successfully, but these errors were encountered:
Also, even if we workaround the uid/gid problem (cf decription), I noticed that runner cannot talk to zookeeper and so is still not detected as running. If you log into runner container, hosts are not resolved anymore:
$ ping containerhost
ping: containerhost: Name or service not known
I noticed that bootstrapper mounts /run into the container since 2.13 and if I start the runner container manually without mounting /run, I can well resolve hosts.
Starting 2.13 and above (including 3.0 and above), ECE does not bootstrap on SLES 12 and 15, with docker 19 or 20:
Details
bootstrap logs:
in docker logs of runner:
What I noticed is ece user is well in passwd and group, and
elastic
well belongs toece
group! So this failure should not happen.Indeed, path to
runner.conf
:On ubuntu, user
ece
is well set as owner of/elastic_cloud_apps/runner
, but on SLES it shows its uid 199For bootstrapper docker container, it's well displayed
ece
and not its uidAlso, the following command does not work:
This does not make sense as
ece
user is well defined in/etc/passwd
Again, it's all good on ubuntu and on SLES from inside boostrapper container
My guess is that docker have issues with mapping uid/gid between the host and the container. Indeed, the user/group
ece
does not exists on the host. And so,elastic
does not belong to groupece
on the host.Workaround
On the host, create a user and group named
ece
with uid/gid both199
, and add userelastic
toece
group.Then run ECE installer, and that should work!
The text was updated successfully, but these errors were encountered: