CI Failure - Envoy

Open
#1,882 0 comments 0 reactions 1 assignee View on GitHub

@MihaZupan is already working on this.

Since Aug 4, 2023.

Assessment

This issue has not been assessed yet.

Description

There is no base image for scheme-http-http-https-http2 defined here:
https://github.com/aspnet/Benchmarks/blob/37be8e1a1b3cbafbbdd1c8c9c267e63bff5488ce/build/proxies-scenarios.yml#L117

The docker file should either have a new entry or Envoy should not be benchmarked for this combination:
https://github.com/aspnet/Benchmarks/blob/main/docker/envoy/envoy.dockerfile#L30

docker build --pull --build-arg SERVER_SCHEME=http --build-arg SERVER_PROTOCOL=http --build-arg DOWNSTREAM_SCHEME=https --build-arg DOWNSTREAM_PROTOCOL=http2  -t benchmarks_envoy-reverseproxy -f docker/envoy/envoy.dockerfile /tmp/benchmarks-agent/benchmarks-server-1/yzc5z521.pca/docker/envoy
Sending build context to Docker daemon  25.09kB

Step 1/25 : ARG SERVER_SCHEME=http
Step 2/25 : ARG SERVER_PROTOCOL=http
Step 3/25 : ARG DOWNSTREAM_SCHEME=http
Step 4/25 : ARG DOWNSTREAM_PROTOCOL=http
Step 5/25 : FROM envoyproxy/envoy-dev:latest AS base
latest: Pulling from envoyproxy/envoy-dev
Digest: sha256:19e8d6195755c6f098fab73448cef7682befb0d03ad02039be1057a3ba09d41f
Status: Image is up to date for envoyproxy/envoy-dev:latest
 ---> de4d537fbe7c
Step 6/25 : ENV DOWNSTREAM_ADDRESS tfb-database
 ---> Using cache
 ---> 4f58cbf88f26
Step 7/25 : ENV DOWNSTREAM_PORT 5000
 ---> Using cache
 ---> 91388841a843
Step 8/25 : ADD testCert.crt /etc/testCert.crt
 ---> Using cache
 ---> 5dfedd47b2b4
Step 9/25 : ADD testCert.rsa /etc/testCert.key
 ---> Using cache
 ---> ae2e5a13b1f4
Step 10/25 : ADD run.sh /
 ---> Using cache
 ---> 80dc6efc8c6d
Step 11/25 : RUN chmod +x /run.sh
 ---> Using cache
 ---> 4369953c396e
Step 12/25 : FROM base AS scheme-http-http-to-http-http
 ---> 4369953c396e
Step 13/25 : ADD envoy-http.yaml /etc/envoy.yaml
 ---> Using cache
 ---> c1f799b2b1ac
Step 14/25 : FROM base AS scheme-https-http-to-http-http
 ---> 4369953c396e
Step 15/25 : ADD envoy-https-http.yaml /etc/envoy.yaml
 ---> Using cache
 ---> 23d9e67fe6c6
Step 16/25 : FROM base AS scheme-https-http-to-https-http
 ---> 4369953c396e
Step 17/25 : ADD envoy-https-https.yaml /etc/envoy.yaml
 ---> 5be6e3f1284d
Step 18/25 : FROM base AS scheme-https-http2-to-https-http2
 ---> 4369953c396e
Step 19/25 : ADD envoy-http2.yaml /etc/envoy.yaml
 ---> Using cache
 ---> d7085c6bb0e2
Step 20/25 : FROM base AS scheme-https-http2-to-http-http
 ---> 4369953c396e
Step 21/25 : ADD envoy-https-http.yaml /etc/envoy.yaml
 ---> Using cache
 ---> 23d9e67fe6c6
Step 22/25 : FROM base AS scheme-https-grpc-to-https-grpc
 ---> 4369953c396e
Step 23/25 : ADD envoy-grpc.yaml /etc/envoy.yaml
 ---> Using cache
 ---> b9150dc2e880
Step 24/25 : FROM scheme-${SERVER_SCHEME}-${SERVER_PROTOCOL}-to-${DOWNSTREAM_SCHEME}-${DOWNSTREAM_PROTOCOL} AS final
pull access denied for scheme-http-http-to-https-http2, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
Dominant language
C#
Stars
1.2k
Forks
244
Avg merge
4d 4h
Merged PRs (30d)
7

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aspnet/Benchmarks

All issues in aspnet/Benchmarks

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.