Skip to content
This repository was archived by the owner on Jan 8, 2024. It is now read-only.
This repository was archived by the owner on Jan 8, 2024. It is now read-only.

Registry insecure flag #3333

@marcotuna

Description

@marcotuna

Describe the bug
When attempting to upload a container image to a self hosted container registry using the registry container, which runs on http by default, waypoint is not able to upload the container image to it even when specifying the insecure = true flag
https://www.waypointproject.io/plugins/docker#insecure

❌ Pushing Docker image...
 │ The push refers to repository [192.168.0.38:5000/app]
! unable to stream Docker logs to terminal: Get
  "https://192.168.0.38:5000/v2/": http: server gave HTTP response
  to HTTPS client

Steps to Reproduce

  • Run the private container registry
docker run -d -p 5000:5000 --restart always --name registry registry:2
  • Configure a waypoint template file pointing to that container registry
registry {
    use "docker" {
        image    = "192.168.0.38:5000/app"
        tag      = "latest"
        insecure = true
    }
}

Expected behavior
The container image should be uploaded when insecure = true flag is enabled and using an http container registry.

Waypoint Platform Versions
Additional version and platform information to help triage the issue if
applicable:

  • Waypoint CLI Version: 0.8.1
  • Waypoint Server Platform and Version: nomad
  • Waypoint Plugin: n/a

Additional context
When using the below configuration it works successfully:

registry {
        use "docker" {
            image    = "localhost:5000/app"
            tag      = "latest"
            insecure = true
        }
}

Use case:

  • Allow to upload container images to on-prem self hosted container registries

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions