-
Notifications
You must be signed in to change notification settings - Fork 530
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
Add nosse42
images
#103
Comments
@torarnv can you try the following image tags and see if they run on your NAS without segfault? I don't have a non-SSE-4.2 system...
If they work, then I'll put this tooling on Travis and formally release them (and will delete those |
Seems to work! Only tried the bionic one, but whereas |
I force-pushed an update commit because of a bad commit message. Generally a no-no but don't expect anybody to have cloned the repo in the last 8 minutes. Hopefully I'm not proven wrong. |
These are tagged:
I'm waiting for any other news before tagging an RC. |
Thanks @neomantra !! |
Can you please add buster-nosse42 or disco-nosse42? Some packages (like libcjson1) are not available in older ubuntu versions. |
@yangzhaofeng I added a You'll be able to try out I'm not going to release any |
@neomantra Currently the device is not available, for we are starting our lunar new year holiday today and will come back to company two weeks later. I will test the two images as soon as possible after I return. Currently I was using a workaround running openresty (alpine-fat-nosse42) and other programs in different docker containers (the other in debian:buster) and communicate with exec.sock in the same docker volume. |
There are now also |
By default, OpenResty builds with SSE 4.2 optimizations enabled. Platforms which don't support SSE 4.2 need an image without that enabled. Add these as flavors to the automated build.
One motivation for this (versus forcing these subset of users to build their own) is that the non-SSE platforms are often embedded systems on which build might be a pain. Plus, why should they learn about building images and nuances when they just want an app server on their NAS...
So if Travis can support this easily, let's add it.
The text was updated successfully, but these errors were encountered: