-
Notifications
You must be signed in to change notification settings - Fork 128
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
GLIBC on build machine too recent for Ubuntu 18.04 LTS #41
Comments
As far as I could see using |
not AFAIK |
On which OS was the
Example: I have two machines: If I build the |
Contributed on behalf of STMicroelectronics Signed-off-by: Johannes Faltermeier <jfaltermeier@eclipsesource.com>
The Linux build is done like this: Line 17 in 850fe09
So we are using the thegecko/theia-dev image to build, which is built from https://github.com/eclipse-theia/theia-blueprint/blob/master/Dockerfile as far as I could see. So currently this is Debian Buster If we deploy a new version of this image using the Dockerfile from #46 we should have compatibility with more Unix Versions. |
Yes, https://github.com/eclipse-theia/theia-blueprint/blob/master/Dockerfile. It should probably be published somewhere else. Anyone aware of a docker registry owned by Theia or Eclipse we can use? |
I found this in the eclipse project handbook: https://wiki.eclipse.org/CBI#Docker_Hub |
Let's just be aware of this limitation. We might eventually consider adding OS-specific builds to improve compatibility: e.g. RHEL7+, Ubuntu LTS, ... |
@thegecko I've been thinking that we should consider creating the next generation of "theia-apps" under the foundation. The original one is licensed Apache 2 and I think it probably can't be practically re-licensed, because it has a lot of external contributions. OTOH the use of We would publish these under the Foundation's account, on (*): Teaser: I'd like to have a packaged browser version of WDYT? |
Yeah, good idea. My only concern would be the effort to produce these and ongoing maintenance. How do we ensure they don't rot? To solve this issue of hosting the linux build machine (and considering the potential future images you suggest), should we request an |
I guess the same way we do for images under theia-apps: have a minimal test suite that detects if the image is borked and generally maintain them. @vince-fugnitto and myself have been doing most of that work (not a huge effort), and we could transition to the new images. The idea would be to do them from scratch or at least not based on our existing images. |
sounds like a good idea! |
Use older debian version for build #41
Bug Description:
When starting the AppImage on Ubuntu 18.04 we get this error:
Steps to Reproduce:
The text was updated successfully, but these errors were encountered: