ansible-interactive-tutorial icon indicating copy to clipboard operation
ansible-interactive-tutorial copied to clipboard

Lesson Menu doesn´t show up in Ubuntu 18.04.2 LTS (Bionic Beaver) Subsystem for Windows 10

Open FelixRodriguezJara opened this issue 5 years ago • 7 comments

Hello Turkenh!

Fist of all, thank you very much for writting the tutorial. I am trying to use it in Ubuntu 18.04.2 LTS that comes with Windows 10. As you can see, Docker works fine and starts the containers, however, the Lesson menu doesn´t show up and you can´t pick any lesson, see traces below:

root@Felix-Rodriguez:/mnt/d/Felix/Tech/Ansible/ansible-interactive-tutorial-master# ./tutorial.sh creating network ansible.tutorial starting container host0.example.org: mapping hostport 42726 -> container port 80 && hostport 42729 -> container port 8080 starting container host1.example.org: mapping hostport 42727 -> container port 80 && hostport 42730 -> container port 30000 starting container host2.example.org: mapping hostport 42728 -> container port 80 && hostport 42731 -> container port 443 starting container ansible.tutorial

== ==

(Comment - According to the video, the lessons menu should be displayed here, but it's not)

  1. [Exit]

Please select a lesson: 1 (ENTER, nothing happens)

Please select a lesson: 1 (ENTER, nothing happens)

Please select a lesson:

The only selection that works is exit. Do you know why could this be happening?

Thank you very much.

Kind regards.

FelixRodriguezJara avatar Jun 05 '19 22:06 FelixRodriguezJara

For me with Win10 and Powershell menu opens then closes automatically. Tried to run it from Git bash , it complains about tty and suggest to use winpty. Tried ,not worked either. So in Hyperv I created an Ubuntu as virt machine and runnning it from there. It works well with same type of Ubuntu.

ghost avatar Jun 06 '19 15:06 ghost

Thank you for your answer, atekka85epam! Yes, that was the behaviour for me too, I was trying to avoid having to create a new VM, that´s why I tried with the Windows 10 UNIX subsystem.

Thank you!

FelixRodriguezJara avatar Jun 07 '19 09:06 FelixRodriguezJara

Other open issues seems to be related but I could not find time to work on this yet.

Also please note, you can always run the tutorial on http://play-with-docker.com

turkenh avatar Jun 12 '19 21:06 turkenh

Ah, this one is different than other issues, I'll try to find a similar setup and try to reproduce.

turkenh avatar Jun 12 '19 21:06 turkenh

Thank you! Keep me posted.

Kind regards.

On Wed, 12 Jun 2019, 23:48 Hasan Turken, [email protected] wrote:

Ah, this one is different than other issues, I'll try to find a similar setup and try to reproduce.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/turkenh/ansible-interactive-tutorial/issues/25?email_source=notifications&email_token=AMIK6YXHI2FAKZYL6DAPSJLP2FVKBA5CNFSM4HUMS26KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXR4TII#issuecomment-501467553, or mute the thread https://github.com/notifications/unsubscribe-auth/AMIK6YQDVCMMX4G7H4VW7PDP2FVKBANCNFSM4HUMS26A .

FelixRodriguezJara avatar Jun 13 '19 06:06 FelixRodriguezJara

This issue still exists. It looks like it has something to do with mounted paths: image

dwettstein avatar Apr 08 '21 06:04 dwettstein

OK, got it to run using a workaround. I simply replaced the paths within the file tutorial.sh to absolute Windows paths (double backslash instead forward slash).

On my machine (Windows, using Git For Windows Bash) the variable BASEDIR is set to /c/Users/my-user/ansible-interactive-tutorial. So I added the following to the file tutorial.sh:

BASEDIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
BASEDIR_WIN="C:\\Users\\my-user\\ansible-interactive-tutorial"

NOF_HOSTS=3
NETWORK_NAME="ansible.tutorial"
WORKSPACE="${BASEDIR}/workspace"
WORKSPACE_WIN="${BASEDIR_WIN}\\workspace"
TUTORIALS_FOLDER="${BASEDIR}/tutorials"
TUTORIALS_FOLDER_WIN="${BASEDIR_WIN}\\tutorials"

And within the function runTutorialContainer, I referenced to the *_WIN variables for the docker run command.

See also:

  • https://stackoverflow.com/questions/41394822/docker-invalid-characters-for-local-volume-name

dwettstein avatar Apr 08 '21 06:04 dwettstein