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

How to enable docker insecure-registries on OSIE #178

Open
bingzhangdai opened this issue Aug 14, 2023 · 1 comment
Open

How to enable docker insecure-registries on OSIE #178

bingzhangdai opened this issue Aug 14, 2023 · 1 comment

Comments

@bingzhangdai
Copy link

I have an internal docker registry which uses HTTP protocol. Whenever we use internal tagged images in Actions, the installation process will get stuck. I then tried to pull the image from the console, it said "http: server gave HTTP resposne to HTTPS client".

Expected Behaviour

can successfully pull the image

Current Behaviour

Error response from daemon

Possible Solution

passing args from server to hook.

Steps to Reproduce (for bugs)

  1. build or retag the action images and push them to local registries
  2. local registries are using http protocol
  3. use these images in action

Context

Your Environment

  • Operating System and version (e.g. Linux, Windows, MacOS):

  • How are you running Tinkerbell? Using Vagrant & VirtualBox, Vagrant & Libvirt, on Packet using Terraform, or give details:

  • Link to your project or a code example to reproduce issue:

@jacobweinstock
Copy link
Member

Hey @bingzhangdai. Insecure docker registries are supported via the kernel parameter insecure_registries=registry.example.com:5000,second.example.com:5000 (comma-separated). This can be set via the Boots cli flag --extra-kernel-args.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants