Hi!
(Apologies if this is the wrong place to ask.)
I'm trying to use a publically available base image, but sbt-jib seems to insist on trying to authenticate. Is there a way to avoid that?
For for reference I'm using
jibBaseImage := "phusion/baseimage:focal-1.1.0@sha256:12aeeecfff1a6af0b3b65291aba13f7641d1f3fd6d6c4098507702f33c03c096",
and happen to have a .docker/config.json with credentials for registry-1.docker.io and get
[error] (... / jibImageBuild) com.google.cloud.tools.jib.api.RegistryAuthenticationFailedException: Failed to authenticate with registry registry-1.docker.io/phusion/baseimage because: 401 Unauthorized
[error] GET https://auth.docker.io/token?service=registry.docker.io&scope=repository:phusion/baseimage:pull
[error] {"details":"incorrect username or password"}
(Presumably the problem here is the scope... My credentials have nothing to do with the 'phusion/baseimage' repository -- they're for our own repository.)
Hi!
(Apologies if this is the wrong place to ask.)
I'm trying to use a publically available base image, but sbt-jib seems to insist on trying to authenticate. Is there a way to avoid that?
For for reference I'm using
and happen to have a
.docker/config.jsonwith credentials for registry-1.docker.io and get(Presumably the problem here is the scope... My credentials have nothing to do with the 'phusion/baseimage' repository -- they're for our own repository.)