-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Elastic-agent] .ASC files not being packaged into the Docker images #21320
Comments
Pinging @elastic/ingest-management (Team:Ingest Management) |
@michalpristas @ruflin @blakerouse Any idea how we could solve that for dockers images? I am reluctant to disable the asc check in the docker images but maybe its the only solution. |
I don't know enough about the build process, but I assume that the docker image comes with metricbeat and filebeat built into it, so I would think adding the .asc files to it should follow the same path? |
copied from a slack thread:
3 errors second one: verifier check downloaded signature for included binary invalid signature: hash tag doesn't match third one it tries to download snapshot asc from official store, this one is expected. cause for a second one might be that as asc file is missing it tries to download from latest snapshot, but it might differ (latest asc with stored tar) |
@michalpristas I believe the docker images are created and bundled by us as part of the beat build process, so this could explain why they do not have their asc files? |
The template for the docker images can be found here: https://github.com/elastic/beats/blob/master/dev-tools/packaging/templates/docker/Dockerfile.elastic-agent.tmpl |
this should fix the issue |
@michalpristas Do you have an issue open with them? |
build is ok now, i fetched some intermediate build before postprocess job finished bundling. all good now |
Are the images already created? I can confirm today's builds do not fetch the images with the ASC files: https://beats-ci.elastic.co/blue/organizations/jenkins/e2e-tests%2Fe2e-testing-mbp/detail/master/340/pipeline/337
|
Manu confirmed in slack today that this is fixed as far as the e2e-testing run goes. closing it out |
Log error when running the image to enroll the agent:
It seems that the .ASC is not present in none of the expected locations: filesystem or artifactory. So no process is able to start
Originally posted by @mdelapenya in #21120 (comment)
The text was updated successfully, but these errors were encountered: