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.

Sign up for GitHub

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

Jump to bottom

LXD setup for mist #1020

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

LXD setup for mist #1020

mmmccain opened this issue Jan 26, 2022 · 4 comments

Comments

@mmmccain
Copy link

mmmccain commented Jan 26, 2022 •
edited
Loading

I have mist set up, connected to Linode and to LXD. I can spin up new Linodes or LXD containers. The LXD containers I create can find the internet, update and I set a simple NAT route for a web server to make sure that works. Solid.

What does not work is the networking back to mist from the container and I am not sure why. It will not open a shell and does not provide stats back.

It would be great to document a step by step optimal LXD set up on mist for cloud environments. This is a huge value to anyone managing more then 2 busy instances. With help here, if I can get it down solid, I will produce a "how to" video.
@mmmccain
Copy link
Author

...by manually adding the scripts, I now have monitoring in the containers. Before I start building VLANS I will wait for a reply from someone in the community. I would suspect mist knows how to handle this out of the box and I am missing something.

@Eis-D-Z
Copy link
Contributor

Eis-D-Z commented Feb 2, 2022

The ssh for containers unfortunately broke and we are currently fixing it. In general it is fully functional with access to any lxd container. (Technically it does leverages the lxd rest api to open an exec sh and tunnel it through a websocket)

@mmmccain
Copy link
Author

mmmccain commented Feb 2, 2022

Thank you! This is actually good news as this is a bit of a show stopper, but knowing your method is encouraging as it takes LXC networking completely out of the equation and allows us to focus on building the reverse proxy our use case will need and ansible scripts to complete the set up.

Are you executing scripts in the same manner?

@Eis-D-Z
Copy link
Contributor

Eis-D-Z commented Feb 8, 2022

Scripts work through ssh at the moment but it is in our plans to make it work through exec calls. The next release will have the shell issues fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Eis-D-Z @mmmccain