Open codefromthecrypt opened 3 years ago
Can we please get an update on this?
weird i thought i commented earlier - seems not
we currently publish debs to our release page
when i find some time i will add an apt repo to make those available via apt install
there are no current plans to publish rpms
as commented previously, these are statically compiled binaries - the same binaries that are available in the docker container and for direct download from the release page, just with deb packaging
Why cant we use these packages from the github releases? https://github.com/envoyproxy/envoy/releases/download/v1.30.1/envoy-1.30.1-linux-x86_64 ?
Why cant we use these packages from the github releases?
you can - but you cant install them with dpkg/apt
@phlax maybe this issue can be closed with docs
reason is that this issue will continue to accumulate comments otherwise and I dont see any resolution besides what has been commented.
what do you think?
@phlax There are lot of dependency issues rising when we use the releases binary. wrt gnu library for various linux versions
./envoy: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by ./envoy)
./envoy: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by ./envoy)
./envoy: /lib64/libpthread.so.0: version `GLIBC_2.30' not found (required by ./envoy)
./envoy: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by ./envoy)
@codefromthecrypt would be happy to review a docs PR
this bit is incorrect tho
no plans to publish deb or rpm from canonical repos
there is a plan to publish a deb/apt repo, its just not that high priority right now
@sivatarunp you need to use a sufficiently new enough distro that has a compatible glibc
there is a plan to publish a deb/apt repo, its just not that high priority right now
@phlax so I guess we should keep this open then, as I don't expect much value in creating another issue as "official" sort of means canonical. Thanks for the input!
Title: Provide official debian and RPM packages
Description: Right now, everything on the website mentioning "getenvoy" can be removed without breaking people.. except debian and RPM packages.
Can you please host official debian and RPM packages? Seems they can be built from the same binaries used to make docker images similar to #16830
Once this is done, hopefully there's no need for confusion anymore as getenvoy's build and packaging pipeline can quietly turn off.
Relevant Links: https://github.com/envoyproxy/envoy/issues/16830