-
Notifications
You must be signed in to change notification settings - Fork 225
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
Try testing in container #816
base: main
Are you sure you want to change the base?
Conversation
f16de40
to
feb995e
Compare
Hi @coolaj86, Could you please approve the workflow? |
feb995e
to
043965d
Compare
Hi @virzak, Thanks for looking into this. I'm now available to focus on Webi during the next 2-3 weeks. If you're also available, I'll have a quick turn around time to work with you on this. |
@coolaj86 let's do it! |
It looks like what you have here is simply creating a container, copying a curl binary into it, and then running webi on the fresh system to see if it installs Where do you want to take it? I think my ideal would be something like:
I also have a High-Availability Proxmox cluster where I can create LXCs within a matter of a few seconds (I could even preallocate some), and delete them just as easily. That could be much faster than GitHub Actions, and give access to any environment... but also comes at the cost of development. |
This was just a first investigation step. The intention was to expose #814 during build. Since this workflow was just recently approved I didn't know how long this would take. It also looks like curl needs more permissions, so I'll try to modify it. Definitely if it takes too long, perhaps there needs to be a different strategy. |
c291235
to
7cd7f15
Compare
After fixing the permission issue, the container seems to be taking about 5-6 seconds. |
Try installing 7.3 instead of latest / 7.4 |
No description provided.