Request to update documentation regarding - 401 unauthorized #2561
Comments
|
The image reference determines the server URL of the target registry. In this regard, typing an image reference in Jib is very similar to typing a web server URL in the address bar of a web browser; each server uses different URL paths to access their resources, and it's basically the user's responsibility to know which URL and path to type to access a resource on the server they want. To clarify, it is not that an image reference must contain a username. However, I think it does make sense to improve our FAQ about 401 unauthorized on this front, because people owning top-level Docker Hub repositories will already know very well what they are doing; only those people inexperienced in Docker will hit this type of hiccup. More details about image reference format: Technically, an image reference is completely free-form; you can use whatever format you want (as long as syntactically acceptable), be it Examples:
|
|
Forgot to close this back then. I think there's no need to update the code or doc. The user misunderstanding was the source of the confusion. |
Environment:
Description of the issue:
Not specifying the username in --image parameter results in 401 unauthorized
Steps to reproduce:
jib-gradle-pluginConfiguration:plugins { java kotlin("jvm") kotlin("plugin.spring") version "1.3.72" id("org.springframework.boot") version "2.3.1.RELEASE" id("io.spring.dependency-management") version "1.0.9.RELEASE" id("com.google.cloud.tools.jib") } group = "guru.springframework" version = "1.0-SNAPSHOT" configure<JavaPluginConvention> { sourceCompatibility = JavaVersion.VERSION_1_8 } repositories { jcenter() } dependencies { implementation("org.jetbrains.kotlin:kotlin-stdlib-jdk8") testImplementation(group= "junit", name= "junit", version= "4.12") testImplementation("org.junit.jupiter:junit-jupiter:5.6.2") implementation("org.springframework.boot:spring-boot-starter-data-jpa:2.3.1.RELEASE") implementation("org.springframework.boot:spring-boot-starter-security:2.3.1.RELEASE") implementation("org.springframework.boot:spring-boot-starter-thymeleaf:2.3.1.RELEASE") implementation("org.springframework.boot:spring-boot-starter-web:2.3.1.RELEASE") implementation("org.webjars:bootstrap:4.5.0") implementation("org.webjars:jquery:3.5.1") implementation("com.h2database:h2:1.4.200") testImplementation( "org.springframework.boot:spring-boot-starter-test:2.3.1.RELEASE") } tasks { compileKotlin { kotlinOptions.jvmTarget = "1.8" } compileTestKotlin { kotlinOptions.jvmTarget = "1.8" } } jib.to.image = "docdodoc/catalogapp" jib.to.credHelper = "wincred"Log output:
Additional Information:
gradlew catalogapp:jib --image=catalogapp_docker --stacktraceDoesnt Work As I didn't pass my username, and this value was overriding my configured image name in gradlegradlew catalogapp:jib --stacktraceWorks Takes the image name value provided in gradlegradlew catalogapp:jib --image=<USER_NAME>/catalogapp_docker --stacktraceWorksExpected behavior:
The addition of --image argument which overrides the existing value from the
jib.to.imageshould be notified/logged.In the documentation, it would be better to modify the image command to include the <USER_NAME> field as well.
like this.
gradle jib --image=<USER_NAME>/<IMAGE_NAME>The text was updated successfully, but these errors were encountered: