Closed YvesZHI closed 1 year ago
github repository of Envoy has always been tested?
the images that are built in CI and published to dockerhub are tested - at least the ubuntu one is - pretty extensively
without trying to track the exact issue, it looks to me like you are mixing versions of config and and docker images
if you are using example configs, or downloading them, try to make sure that they match the version of envoy that you are testing
if that is not the case - im happy to try and figure out what is going wrong
@phlax Thanks dude, you are totally right. git clone
is not enough, I need to checkout to a verified tag.
I want to try to do some tiny enhancement for Envoy so I tried to build an Docker image of Envoy from source code.
Here is what I've done on my Ubuntu server:
Now I can see an Envoy docker image has been built. Here is the output of
sudo docker images
:So the first line is just what I built, the second line is the official Envoy image, which has been downloaded before.
Then I made a docker-compose yaml file:
Besides, I downloaded a hello-world yaml config file from here: https://www.envoyproxy.io/docs/envoy/v1.25.1/start/quick-start/run-envoy.
However, when I execute
sudo docker compose run --rm --service-ports envoyv
to validate the hello-world yaml config file, I always get the error:But if use the official Docker image (
image: envoyproxy/envoy:v1.22-latest
in the docker-compose yaml file), everything would be fine.So it seem that I built an Docker image with some bugs...
Did I do something wrong? Or is there some bug on the main branch of the github repository of Envoy?