-
-
Notifications
You must be signed in to change notification settings - Fork 499
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
wings: Skip the virtualization warnings #160
Comments
Docker in LXC is not officially supported by Docker. Many people will have trouble with installing with the script, so I would keep the warning. |
The script is doing what the |
The panel may run on LXC and OpenVZ and as far as I know, there is no check that prevents that. Wings, however, require Docker which most likely won't run with LXC or OpenVZ. I am not sure about LXC, but Virtuozzo has "experimental support" that requires the host machine to enable it (see this). Closing. |
Idk if i can re-open this issue, but many hosters are using Proxmox to create Containers LXC. And it's only a box to check to make nesting (Docker) working. Pterodactyl is running perfectly with this box checked. A lot of french hosts are especially allowing docker on their lxc hosting offers. This is why i proposed to add an argument like --ignore-lxc or others, to allow pterodactyl to be installed on these containers. |
I didn't have a lot of skills in Bash to modify the script and ignore this warning, so it's why i asked for it. |
Ah, I see. I'll reopen the issue but I am yet to decide if this is going to be implemented. I see the use case and I understand it's frustrating that the script doesn't let the user override the check. We'll definitely change something, but maybe not in the form of a command line option! 🙂 In the meantime, you can remove this line to override the check. https://github.com/vilhelmprytz/pterodactyl-installer/blob/600d8dc78adb0b0069618a5b03cd7469e6778c2c/install-wings.sh#L237 |
Thanks :) |
Add an argument to allow installing on LXC because it works :)
The text was updated successfully, but these errors were encountered: