Skip to content
New issue

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

LXD init breaks the mist.io shell #1019

Open
mmmccain opened this issue Jan 26, 2022 · 3 comments
Open

LXD init breaks the mist.io shell #1019

mmmccain opened this issue Jan 26, 2022 · 3 comments

Comments

@mmmccain
Copy link

I stood up Ubuntu 20.04 from mist, opened the shell and executed lxd init. About half way through the script it asks for an IP address to be entered. The mist shell does not display this correctly and it will not accept even the default (CR). It just breaks the script.

This is very easy to reproduce and it is consistent.

Work around is to ssh to install lxd. This is the only thing I have seen the mist shell have a problem with so far.

@Eis-D-Z
Copy link
Contributor

Eis-D-Z commented Feb 2, 2022

I will kindly ask for some clarifications.
The Ubuntu machine was hosted on Linode?
By not being the IP displayed correctly, it means that you typed eg. 192.149.233.22 and something else showed on screen?
I am understanding that because the IP that got typed did not go through properly, the script also crashed because it expected to receive an IP but it got something else, correct?

@mmmccain
Copy link
Author

mmmccain commented Feb 2, 2022

I do wish I had grabbed a screen shot.

This is an STTY issue in SSH. It is receiving a set of characters from the from the shell script "lxd init" that it can not interrupt correctly. Once the shell receives these characters, which makes the line no longer fully readable, it will not receive any text input of any kind, not even a carriage return. ...and yes, it will not let you type an IP address. Nothing is shown on the screen.

@Eis-D-Z
Copy link
Contributor

Eis-D-Z commented Feb 4, 2022

We found the issue and we are fixing it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants