Azure provider - sudo: unable to resolve host

[ResistanceIsUseless]

this issue doesn't break anything(that im aware of) but it should be an easy fix to add the hostname with 127.0.0.1 to /etc/hosts during build.

something like: hostname=$(cat /etc/hostname) && echo "127.0.0.1 $hostname" >> /etc/hosts

[pdelteil]

Hello,

How can I reproduce this error?

[ResistanceIsUseless]

Just switch to azure, should happen with all images using the default ubuntu image.

As well as running a sudo command...

[0xtavian]

@ResistanceIsUseless This error seems to have come from replacing Azure's resolv.conf with ours. It seems this error, and a possible recent change to azure's ubuntu 20.04 image and cli/api, broke linux controllers using the azure provider. There is a temp patch here.

[pdelteil]

So, what you need to do is:

• Remove all instances (axiom-rm '\*' -f)
• Switch to azure branch (git checkout azure)
• Rebuild axiom (axiom-build)
• Start new fleet (axiom-fleet NAME -i 10)
• Select instances (axiom-select *)

That's all!

[0xtavian]

So, what you need to do is:

• Remove all instances (axiom-rm '\*' -f)
• Switch to azure branch (git checkout azure)
• Rebuild axiom (axiom-build)
• Start new fleet (axiom-fleet NAME -i 10)
• Select instances (axiom-select *)

That's all!

Correct. I hope to fix this in master sometime over the weekend. Also you can run axiom-fleet -i 10 now, axiom will pick a random fleet prefix.

[pdelteil]

Yes, I don't like the fleet prefixes because I re use scripts with the same fleet name. :D

[0xtavian]

@ResistanceIsUseless @pdelteil I pushed the fix to master yesterday. To update run axiom-update on the master branch and then run axiom-build. Im going to close this issue but lmk if you run into any problems.

[ResistanceIsUseless]

I'll test and let you know if I see any issues. Thanks!

[0xtavian]

My finger slipped, ever so slightly, and I accidentally re-open the issue