after selecting menu no shell prompt
deknos opened this issue · 14 comments
Hi,
i used your tutorial yesterday. It is really cool! :)
Today i tried to reset it, first with
git clean -fdx ; git reset --hard ; docker system prune -a ; ./tutorial.sh --remove
and then i restarted it.
now if i enter a menu point the shell prompt does not appear, only after tipping CTRL+C.
any idea?
i did:
git clean -fdx ; git reset --hard ; ./tutorial.sh --remove ; ./tutorial.sh und exit it with 0.
then i ran ./tutorial.sh --test and it seems to stop at after executing ansible-playbook -i hosts -l host1.example.org. apache.yml.
any idea? :)
Could you find a solution?
./tutorial.sh --test may sporadically fail with no response, this is a known issue caused by nutsh.
sadly no, because i am not sure how to debug it. it normally happens the first time at lection 3 or 4 and with CTRL+C and it seems to work then.
only pressing Enter does not seem to help. and hitting more times CTRL+C prints only the "enter exit to terminate the nutshell"
On which system do you do this? i work on debian stable (9.x)
I am running on mac.
Can you please try on http://play-with-docker.com ?
I have the same behaviour there. start a new instance, clone it, start ./tutorial.sh and choose 6 the shell prompt does not return. it stays on "== Playbooks, pushing files on nodes =="
with CTRL+C and Enter i see the next step again. how do i do strace in docker? :D
This is really strange, because I cannot reproduce on play-with-docker as well. Selecting 6 and hitting enter simply goes into tutorial.
which browser (and version) do you use? This is really annoying, because i am always anxious to skip a lesson :-D
It was Chrome Version 63.0.3239.132 (Official Build) (64-bit)
just tried on Safari and couldn't reproduce there as well :)
Could you try it with Firefox or Chrome?
git clone ...
./tutorial.sh
exit
./tutorial.sh --remove
git clean -fdx
git reset --hard
./tutorial.sh
6
Still could not reproduce, what am I missing ? :)
Here it is: https://asciinema.org/a/bCUIjUixczMI5qMuHXjNrVNNP
Recorded on play-with-docker with Chrome Version 63.0.3239.132 (Official Build) (64-bit)
Ok, I could observe this several times sporadically. Is it happening always on your side?