E

That's assuming that you run the registry in the same docker engine that runs earthly buildkitd. Is that the case?

Summary

That's assuming that you run the registry in the same docker engine that runs earthly buildkitd. Is that the case?

Status
resolved
Tags
    Source
    #earthly
      s

      sloury

      10/19/2024

      Here are some notes that don't answer your question BUT may provide valuable information to help you in your task.

      s

      sloury

      10/19/2024

      If you use linux, listening on 0.0.0.0 and pointing to the bridge should be enough. If using windows or mac, it won't work, because of the virtual machine in between the host and docker. In the latter case, the docker provider (colima, orb of docker desktop) provides a way to connect to the host, but there is no generic anwser.

      j

      jorsol

      10/18/2024

      No, it is running on the host started as a local app, I could somewhat workaround it by listening on 0.0.0.0 and use the local IP (192.168.1.x) and then add buildkit_additional_config with http=true

      s

      sloury

      10/18/2024

      That's assuming that you run the registry in the same docker engine that runs earthly buildkitd. Is that the case?