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

Reenable the containers secure basic registry test #42820

Open
baronfel opened this issue Aug 17, 2024 · 0 comments
Open

Reenable the containers secure basic registry test #42820

baronfel opened this issue Aug 17, 2024 · 0 comments
Labels
Area-Containers Related to dotnet SDK containers functionality Test Debt untriaged Request triage from a team member

Comments

@baronfel
Copy link
Member

Is your feature request related to a problem? Please describe.

The containers test that validates secure communications to a local registry uses a certificate generated by the aspnetcore dev-certs tool to configure secure comms between a client and a server. There were some changes to this tool on Linux in 8.0.4xx that have made the test start failing, but we needed to disable the test to unblock servicing flow. We should reenable the test ASAP to ensure we don't regress this behavior.

Describe the solution you'd like

Check out the conversation in #42701 and make the test green again. Things to investigate include directory permissions used by the dev-certs tool on Linux.

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-dotnet test untriaged Request triage from a team member labels Aug 17, 2024
@baronfel baronfel added Area-Containers Related to dotnet SDK containers functionality Test Debt and removed Area-dotnet test labels Aug 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Containers Related to dotnet SDK containers functionality Test Debt untriaged Request triage from a team member
Projects
None yet
Development

No branches or pull requests

1 participant