-
Notifications
You must be signed in to change notification settings - Fork 3
Unable to start Docker Container #2
Comments
/cc @adriancole |
will take a look tomorrow first thing. missed it! |
Thanks! I was having trouble tracing back the container used. Is it using Alpine by any chance? If so.. that could explain the issue. |
we recently changed to normal openjdk...
…On Wed, Aug 8, 2018 at 5:55 AM Ray Tsang ***@***.***> wrote:
Thanks! I was having trouble tracing back the container used. Is it using Alpine by any chance? If so.. that could explain the issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
pushing image zipkin-gcp 0.7.0 now |
if you don't mind, can you q/a for me once it is on dockerhub? I am watching now, so if there's a problem i will see and dig |
i just gave 0.7.0 tag a try, but seeing the same issue. I think the base image is still alpine. I haven't been able to trace the root base image:
|
the base images is this https://github.com/openzipkin/docker-jre-full I will try to run and see |
It is failing on OpenSsl required. Our base image for very long time has been alpine. Perhaps there's a package missing or something new in a later version of grpc that wasn't the case earlier |
I'm very much hoping that netty/netty-tcnative#111 isn't true and grpc isn't unsupported on alpine :P @saturnism say it ain't so! cc @openzipkin/devops-tooling |
afaik, it never supported alpine's libmusl :( For smaller images, I'd recommend |
maybe there was a fallback or something, unless somehow the image was never
tested which seems unlikely.
anyway you are saying we need a custom image huh. that sucks
|
I dont think we want to change all of our images just because grpc uses
something that could but chooses not to support alpine.
what we can do here is copy the config from the base zipkin image, based on
one of the ones mentioned, and make a note about the drift risk.
if the SSL support really never supports alpine then this debt will
continue. ideally considering all the resources on grpc, someone will pitch
in and get alpine supported.
|
Makes sense! The other option is to add glibc to this image. but i don't think there is official support. In the past we had a stackdriver zipkin proxy image that was hosted on Thanks for taking a look! |
one of the things I believe google should be doing while promoting gcp is doing more to help norman. For example, this PR could have gotten alpine.. when there's a surge of demand on projects like netty, it could be good to dig in and help netty/netty-tcnative#252 if that happened, we'd probably have no dillemma right now, but there's still a chance to change the future :) @saturnism can you take this feedback to google? :P |
opened openzipkin/docker-java#9 to track us moving our base image to JRE 11, which will obviate the ssl concern |
I am testing images.. so far zipkin-gcp up to 0.6.0 works. I think something changed where possibly falling back when openssl isn't available changed to crash the server |
zipkin-gcp 0.6.2 works, it started crashing in 0.6.3 |
so this happened when we upgraded from grpc 1.11.0 to 1.13.1. One way out is to revert that.. this is the easiest. then we just upgrade later |
checking to see if this is related to us changing to a different alpine image, which is entirely possible |
ok we are getting somewhere.. our base zipkin image switch from zulu to openjdk jre (both alpine) starting with zipkin 2.9.4. Must be that the zulu image had openssl else the error would have occurred much earlier |
so the original image depended on, so this is why it worked https://hub.docker.com/r/frolvlad/alpine-glibc/~/dockerfile/ |
Spoke with @anuraaga. We are going to save ourselves some time by using ALPN bootstrap for now. Later, we can just update to JDK 11. openzipkin/zipkin-gcp#91 |
tested with a local docker build and works |
ok 0.7.1 should fix this. thanks especially @anuraaga for helping find a way out of this problem without implying lot of temporary image reshuffling. |
tested published image, so hopefully also works for others! |
Yay! That started off fine. Thank you! |
The text was updated successfully, but these errors were encountered: