cannot login to ansible Lab

[morothebest]

cannot login to ansible Lab using : ansible and password for password. i did all steps but could not login in

[spurin]

Hi @morothebest

Please share with me some more information and we'll get this resolved. What OS are you on, whats your userid and can you also provide a copy of your .env file.

Thanks!

[morothebest]

Hi @spurin

[morothebest]

@spurin

[morothebest]

user is ansible Password is : password

[spurin]

Hi @morothebest

Hopefully you have this resolved, if not, you need to change your paths so they start with /host_mnt/c/users

Let me know if you're still having any problems 👍

[morothebest]

hi @spurin

I did the below as per your request:-

gave the below error :

[spurin]

Hi @morothebest

Rename your folder from diveintoansible-lab-master to diveintoansible-lab and you should be good 👍

[morothebest]

i did

it gave the same error

[morothebest]

when i change the .env back to

did not give error as shown below but still cannot login

[spurin]

Okay great. Can you please share the contents of the config directory in your diveintoansible-lab

A screenshot will be fine 👍

[morothebest]

guest name : ansible guest password: password root password: password guest_shell: /bin/bash

[spurin]

Just noted the previous comments, can you please change your .env file back to starting with /host_mnt/c/users for both entries.

It was failing before because the folder was diveintoansible-lab-master instead of diveintoansible-lab

Then, try doing a docker-compose up, after that it should be okay. If it fails please share a new screenshot

[morothebest]

actually i did change the folder name first then the .env as you told me but it gave the same error

[spurin]

Thanks for the update @morothebest

Can you please try running all of the following and share screenshots -

docker run --rm -v /host_mnt/c/users/mourad/diveintoansible-lab/config:/config ubuntu cat /config/guest_name

docker run --rm -v /mnt/c/users/mourad/diveintoansible-lab/config:/config ubuntu cat /config/guest_name

docker run --rm -v /c/users/mourad/diveintoansible-lab/config:/config ubuntu cat /config/guest_name

[morothebest]

[morothebest]

sorry should be the below

[spurin]

Thanks @morothebest

This helped, I'm surprised to see that the third variation worked for you, i.e. /c/users

I haven't seen this in a while and typically it relates to older versions of Windows. Would you please share a screenshot of the output from start/run/winver

We could try switching your config to /c/users at the start and seeing how it goes. If it is an older version of Windows it can be a bit hit/miss.

If it is an older version and updating Windows isn't practical/viable or something you don't want to do (understandably), then there is also the option to run the lab using Google's free cloudshell. You just need a Google account. For this you just press the button to launch on the repo, sign in with Google and follow the short tutorial on the right hand side. This is here - https://github.com/spurin/diveintoansible-lab-gcp-cloudshell

Let me know how you get on and your thoughts

[morothebest]

am using VM with windows 10 is that can cause an issue ?

[spurin]

Hi @morothebest

I mean, click start, choose run and then type winver.

When you say you're running a Windows 10 VM, can you elaborate?

What's the main system that the VM is running on?

[morothebest]

this is the windows 10 on the VM (VMware)

and the below is the main windows 10 that i have on my computer 👎

[spurin]

Hi @morothebest

I really don't recommend running the course inside a VM and most likely, this relates to the issue you're seeing.

You will end up with multiple layers of virtualisation

i.e. Windows -> VMware -> Docker Desktop (which internally uses -> VirtualBox)

The Windows version itself should be fine but, the virtualisation appears to be screwing the volumes mounts.

I recommend at this point that either you install Docker Desktop directly on your Windows system, or, you go with the Google Cloudshell version (online) that I shared the link for.

The Cloudshell experience is great, it's free with a Google account and you'll be up and running without much effort in a few minutes.

If you go down the direct desktop route instead, let me know also.

[morothebest]

Ok noted

i used this GCC and i got the below

is that normal ?

[morothebest]

@spurin it worked now, found that Malwarbytes prevent it from start

thanks lot

[spurin]

@morothebest I think that sometimes Google also refresh their cloudshell image and this can cause problems. I just updated the image, if you try it, it will be fine now.