Files
nomad/e2e/docker/input/auth_static.hcl
Piotr Kazmierczak f9cbaaf6c7 docker: fix a bug where auth for private registries wasn't parsed correctly (#24215)
In #23966 we introduced an official Docker client and did not notice that in
contrast to our previous 3rd party client, the official SDK PullOptions object
expects a base64 encoded JSON with username and password, instead of username/
password pair.
2024-10-16 22:04:54 +02:00

66 lines
1.4 KiB
HCL

# Copyright (c) HashiCorp, Inc.
# SPDX-License-Identifier: BUSL-1.1
# This job runs a docker task using a container stored in a private registry
# configured with file config static authentication. The registry.hcl job should
# be running and healthy before running this job.
variable "registry_address" {
type = string
description = "The HTTP address of the local registry"
default = "localhost"
}
variable "registry_port" {
type = number
description = "The HTTP port of the local registry"
default = "7511"
}
job "auth_static" {
type = "batch"
constraint {
attribute = "${attr.kernel.name}"
value = "linux"
}
group "static" {
reschedule {
attempts = 0
unlimited = false
}
network {
mode = "host"
}
task "echo" {
driver = "docker"
config {
image = "${var.registry_address}:${var.registry_port}/docker.io/library/bash_auth_static:private"
args = ["echo", "The static auth test is OK!"]
# usename and password come from auth.json in plugin config
}
resources {
cpu = 100
memory = 64
}
}
}
}
# auth.json (must be pointed to by config=<path>/auth.json)
#
# {
# "auths": {
# "127.0.0.1:7511/docker.io/library/bash_auth_static": {
# "auth": "YXV0aF9zdGF0aWNfdXNlcjphdXRoX3N0YXRpY19wYXNz"
# }
# }
# }