Update packages to use Elastic Agent images based on Ubuntu

[mrodm]

Proposed commit message

Once Elastic Agent images based on Wolfi are enabled for testing in 8.16.0-SNAPSHOT (tested here https://github.com/elastic/integrations/pull/10933/files) , there are some packages that their system tests fail for different reasons: permission logs, missing journalctl or not supported package manager.

This PR updates their configuration files to allow use the Elastic Agent images
based on Ubuntu or use user root for tests once it is set to run system tests with Wolfi images by default in #10969.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• [ ] I have verified that all data streams collect metrics or logs.
• [ ] I have added an entry to my package's changelog.yml file.
• [ ] I have verified that Kibana version constraints are current according to guidelines.

Author's Checklist

• [ ]

Related issues

• Closes [iptables] [journald] Errors when testing with Elastic Agent wolfi images #10998
• Closes [apache_tomcat] [microsoft_sqlserver] [stan] Errors when testing with Elastic Agent wolfi images #10999
• Closes [system_audit] Errors when testing with Elastic Agent wolfi images #11000

Screenshots

[jlind23]

I guess that the config below stands for ubuntu images right?

agent:
  base_image: systemd

[mrodm]

I guess that the config below stands for ubuntu images right?

agent:
  base_image: systemd

When that setting is systemd , elastic-package will use the non-complete images, so it would be:
docker.elastic.co/elastic-agent/elastic-agent

If that setting is complete, elastic-package will use the complete image: docker.elastic.co/elastic-agent/elastic-agent-complete

[elasticmachine]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[mrodm]

Moved variants file in order to be considered by elastic-package.
It is expected to be in _dev/deploy folder: https://github.com/elastic/package-spec/blob/aacaf7b19f51d54b394a7640e6898b8398d88cc8/spec/integration/_dev/deploy/spec.yml#L22

[elasticmachine]

Pinging @elastic/sec-deployment-and-devices (Team:Security-Deployment and Devices)

[elasticmachine]

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

[elasticmachine]

Pinging @elastic/sec-linux-platform (Team:Security-Linux Platform)

[jlind23]

I think according to @cmacknz's comment this should rather close all the issues mentioned in the description and not only relate to them.

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 13022f2

History

• 💚 Build #15478 succeeded 7633ddb
• 💚 Build #15467 succeeded db43a82

cc @mrodm

[mrodm]

I think according to @cmacknz's comment this should rather close all the issues mentioned in the description and not only relate to them.

Ok, I'll update the description, so those issues are closed.

Related to the permissions issue found here, there are already two issues in elastic-package that could be interesting:

• Add check about permissions folder for tmp/service_logs elastic-package#1341
• docker-compose service deployer - Provide a volume to share data with elastic-agent elastic-package#1852