search

panamax-rs / panamax

Mirror rustup and crates.io repositories, for offline Rust and cargo usage.
Apache License 2.0
443 stars 46 forks source link

Container Image Fails to run #65

Closed JamesMConroy closed 2 years ago

JamesMConroy commented 2 years ago

When trying to run the latest container image (tag 1.0.6) I get the following symbol issue.

/usr/local/bin/panamax: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.29' not found (required by /usr/local/bin/panamax

This occurs with the init, sync, and serve commands.

JamesMConroy commented 2 years ago

I don't know why but if I build the container myself the error disappears. Maybe it just needs to be rebuilt (or podman does something different from docker)

k3d3 commented 2 years ago

Interesting - I don't understand why that would be happening, considering I'm using the official rust image as a base. The only thing I could think of is I'm running the docker builds on an Arch host, which probably has a newer GLIBC version. But that shouldn't affect what happens inside docker, since that image should have its own GLIBC version.

I'll take a further look into it.

k3d3 commented 2 years ago

Oh, I figured it out. I have a multistage dockerfile which builds with rust:latest and then copies it to debian:latest for hosting. For now I'll just switch both to rust:latest, which kinda defeats the purpose of multistage (to keep docker images small), but that should at least make it work.

k3d3 commented 2 years ago

Now I'm realizing that the rust image is based on the debian image, and my issue was that I had pulled the latest rust but not the latest debian. Doing that has fixed the issues, so I'll just re-push the images.

(at some point I'll have to throw this into Github Actions)

JamesMConroy commented 2 years ago

Yay. I've been meaning to learn GH actions, so I'll take a look at getting a build and test going.

JamesMConroy commented 2 years ago

Created #66 to build and run the image on every push and MR. It should also push it to docker hub.

JamesMConroy commented 2 years ago

With #66 merged this issue should be caught earlier, and this issue can be closed.