[Subscription basic] [nginx] Failing test daily: system test: default (variant: v1) in nginx.stubstatus

[elastic-vault-github-plugin-prod]

• Stack version: Same as in Pull Request builds
• Subscription: basic
• Package: nginx
• Failing test: system test: default (variant: v1)
• DataStream: stubstatus
• Owners:
  • @elastic/obs-infraobs-integrations

Error:

could not setup service: could not boot up service using Docker Compose: running Docker Compose up command failed: exit status 17: failed to solve: process "/bin/sh -c apt-get update && apt-get install -y curl" did not complete successfully: exit code: 100

First build failed: https://buildkite.com/elastic/integrations/builds/28476

Latest failed builds:

• https://buildkite.com/elastic/integrations/builds/28493
• https://buildkite.com/elastic/integrations/builds/28557
• https://buildkite.com/elastic/integrations/builds/28620
• https://buildkite.com/elastic/integrations/builds/28666

[mrodm]

@elastic/obs-infraobs-integrations this kind of errors trying to start the nginx service in the system tests is also happening in elastic-package (e.g. elastic/elastic-package#2726 or elastic/elastic-package#2727):

Example of the error:

 > [nginx 3/4] RUN apt-get update && apt-get install -y curl:
0.311 Ign:1 http://security.debian.org/debian-security buster/updates InRelease
0.314 Ign:2 http://deb.debian.org/debian buster InRelease
0.325 Err:3 http://security.debian.org/debian-security buster/updates Release
0.325   404  Not Found [IP: 151.101.194.132 80]
0.331 Ign:4 http://deb.debian.org/debian buster-updates InRelease
0.343 Err:5 http://deb.debian.org/debian buster Release
0.343   404  Not Found [IP: 151.101.2.132 80]
0.357 Err:6 http://deb.debian.org/debian buster-updates Release
0.357   404  Not Found [IP: 151.101.2.132 80]
0.362 Reading package lists...
0.373 E: The repository 'http://security.debian.org/debian-security buster/updates Release' does not have a Release file.
0.373 E: The repository 'http://deb.debian.org/debian buster Release' does not have a Release file.
0.373 E: The repository 'http://deb.debian.org/debian buster-updates Release' does not have a Release file.
------
failed to solve: process "/bin/sh -c apt-get update && apt-get install -y curl" did not complete successfully: exit code: 100

This is the current Dockerfile for nginx:
https://github.com/elastic/integrations/blob/ddc1f957b60bf15105745ed76b35ef2aa9e73285/packages/nginx/_dev/deploy/docker/Dockerfile

Same error happens in apache package. As an example of one of the issues: #14519

What could it be done to fix these errors in nginx and apache Dockerfiles ? Should the service versions used in tests be updated ?

Maybe related to this announcement: https://lists.debian.org/debian-devel-announce/2025/06/msg00001.html

[ishleenk17]

@mrodm : Someone from the team will look into this

[mrodm]

In elastic-package, Dockerfiles of those test packages will be updated to use versions of nginx and httpd that are based on Debian bullseye elastic/elastic-package#2732

Not sure if you prefer to use other docker tags for those Dockerfiles (or maybe another approach). If other versions are used in the integrations repository (or another approach), elastic-package could be updated accordingly.

And, probably README files of those packages should be updated to set the new versions used for testing. For instance:

• nginx docs mention version 1.19.5 in several sections (link)
• apache docs mention versions 2.4.12 and 2.4.46 (link)

[mrodm]

FYI @lucian-ioan based on this PR elastic/golang-crossbuild#644, it looks like that it can be updated /etc/apt/sources.list file to use archive.debian.org instead, so apt commands work successfully.

Trying that change in elastic/elastic-package#2736, containers can be built and tests can be run successfully too.

I'll keep in elastic-package this PR to keep using the same Docker tags for nginx and apache, and I'll close elastic/elastic-package#2732

And, probably README files of those packages should be updated to set the new versions used for testing. For instance:

• nginx docs mention version 1.19.5 in several sections (link)
• apache docs mention versions 2.4.12 and 2.4.46 (link)

Regarding docs, for apache looks like it is just tested for 2.4.46

integrations/packages/apache/_dev/deploy/variants.yml

Line 3 in e34bc14

SERVICE_VERSION: 2.4.46