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
[root@master ~]# docker run sequenceiq/kylin sh + echo 'Executing scripts from /usr/local/init' + tee /var/log/serf.log Executing scripts from /usr/local/init + for file in '$SERF_INIT_DIR/*' + echo 'Execute: /usr/local/init/00_init.sh' + tee -a /var/log/serf.log Execute: /usr/local/init/00_init.sh + /bin/bash /usr/local/init/00_init.sh + tee -a /var/log/serf.log Basic init has been executed + [[ -n '' ]] + unset SERF_HOSTNAME + '[' -z '' ']' ++ hostname -f + SERF_HOSTNAME=a54f567c914c + sleep 5 + '[' -z a54f567c914c ']' + cat + [[ -n '' ]] + /usr/local/serf/bin/serf agent -config-dir /usr/local/serf/etc sh + tee -a /var/log/serf.log ==> Starting Serf agent... ==> Starting Serf agent RPC... ==> Serf agent running! Node name: 'a54f567c914c' Bind addr: '172.17.0.13:7946' RPC addr: '0.0.0.0:7373' Encrypted: false Snapshot: false Profile: lan ==> Log data will now stream in as it occurs: 2015/05/13 00:27:18 [INFO] agent: Serf agent starting 2015/05/13 00:27:18 [INFO] serf: EventMemberJoin: a54f567c914c 172.17.0.13 2015/05/13 00:27:19 [INFO] agent: Received event: member-join 2015/05/13 00:27:19 [INFO] agent.ipc: Accepted client: 127.0.0.1:30507
then, no response any more
The text was updated successfully, but these errors were encountered:
Are you going to ssh into the running container? I use the "exec" command which works good:
BTW, the kylin docker image has been updated with kylin 0.7.2 release, please try the latest image by following the steps on https://github.com/sequenceiq/docker-kylin
Sorry, something went wrong.
No branches or pull requests
then, no response any more
The text was updated successfully, but these errors were encountered: