Skip to content
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

Add validation of packages installed by the Dockerfiles so that they align with the product #246

Closed
Tracked by #5651
MichaelSimons opened this issue Jun 9, 2017 · 3 comments

Comments

@MichaelSimons
Copy link
Member

MichaelSimons commented Jun 9, 2017

Summary

The packages that are installed by Dockerfiles are defined independently of what the product's actual dependencies are. These should be in sync such that if product dependencies are changed in any way, the Dockerfiles will reflect that change. Today this is a manual process but it can be improved through the work being done in dotnet/core#5651.

Goal

Contributors can use automation to validate that the Linux packages installed in Dockerfiles match up with the official product dependencies.

@MichaelSimons
Copy link
Member Author

@mthalman - Can you log a product issue to define a place where the native dependencies are declared? This is the only way to guarantee the Docker images, snaps, and native linux packages (e.g. debian packages) all include the correct set.

@mthalman
Copy link
Member

I've logged https://github.com/dotnet/coreclr/issues/26303 for the product to provide a way to determine the required package list.

@MichaelSimons MichaelSimons removed their assignment Feb 13, 2020
@mthalman mthalman changed the title Add utest that verifies packages contained in the runtime-deps align with the product Add validation of packages installed by the Dockerfiles so that they align with the product Feb 24, 2021
@mthalman
Copy link
Member

mthalman commented Jan 4, 2023

Closing as this requires more work on dotnet/core#5651 that's not happening any time soon.

@mthalman mthalman closed this as not planned Won't fix, can't repro, duplicate, stale Jan 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

2 participants