Skip to content

Conversation

@jacobweinstock
Copy link
Member

Description

Looking to push through needed/desired code changes from PR #139 and #140. Remove insecure downloading of container registry certificate. Add the ability to specify insecure registries for use in the docker container engine config.

Why is this needed

Fixes: #

How Has This Been Tested?

How are existing users impacted? What migration steps/scripts do we need?

Checklist:

I have:

  • updated the documentation and/or roadmap (if required)
  • added unit or e2e tests
  • provided instructions on how to upgrade

This is not a secure way to download a certificate.
We need to figure out a better way to handle secrets
across the netboot process. For now the certificate
of the container registry must be signed by a known
CA root.

Signed-off-by: Jacob Weinstock <jakobweinstock@gmail.com>
This allows insecure container registries to be used.

Signed-off-by: Jacob Weinstock <jakobweinstock@gmail.com>
@jacobweinstock
Copy link
Member Author

Hey @thebsdbox , would you mind checking this out when you have a moment. Please and thank you!

Forward progress without the daemon.json is not
desired behavior.

Signed-off-by: Jacob Weinstock <jakobweinstock@gmail.com>
@jacobweinstock jacobweinstock added the ready-to-merge Signal to Mergify to merge the PR. label Nov 9, 2022
@jacobweinstock
Copy link
Member Author

@mergify queue

@mergify
Copy link
Contributor

mergify bot commented Nov 9, 2022

queue

✅ The pull request has been merged automatically

The pull request has been merged automatically at 6d43b8b

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready-to-merge Signal to Mergify to merge the PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants