Skip to content
This repository has been archived by the owner on Jun 9, 2020. It is now read-only.

RocksDB state backend causes segfault on Alpine images again #37

Closed
lragnarsson opened this issue Mar 7, 2018 · 6 comments
Closed

RocksDB state backend causes segfault on Alpine images again #37

lragnarsson opened this issue Mar 7, 2018 · 6 comments

Comments

@lragnarsson
Copy link

Seems like the problem in #14 has reappeared at least for 1.4.1-hadoop27-scala_2.11-alpine.

Anyone else experience this?

@iemejia
Copy link
Member

iemejia commented Mar 8, 2018

I confirm this is an issue, it seems to be a regression related to libc6-compat on alpine:3.7. Not sure what would be the best way to proceed, we can repackage libc compatibility by using https://github.com/sgerrand/alpine-pkg-glibc as some Java based containers do, or just remove support for the alpine images until fixed upstream. @patricklucas WDYT ?

@patricklucas
Copy link
Member

I'm not super enthusiastic about keeping alpine support given these persistent issues. The alpine-based image is ~37% smaller than the debian-based image, but that's the only benefit as far as I can tell.

Since users running in production environments are likely building their own images anyway, I'm not sure maintaining support for alpine-based images is all that useful.

We could keep building the alpine-based Dockerfiles in this repo for interested users, but just not publish them to Docker Hub.

@patricklucas
Copy link
Member

@iemejia do you know if this has been fixed upstream? If not, I would move forward with removing the alpine images.

@iemejia
Copy link
Member

iemejia commented Jul 11, 2018

Yes it was solved for Alpine 3.7 and I just tested the latest version 3.8 and it seems to work. So we should be covered once our images are regenerated (they just updated openjdk:8-jre-alpine yesterday to be based on the 'new' alpine 3.8).

@patricklucas
Copy link
Member

👍

@iemejia
Copy link
Member

iemejia commented Jul 12, 2018

I am marking this one close then Hope we don't have this issue anymore.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants