Project

General

Profile

Actions

Bug #22607

closed

arvbox not building

Added by Peter Amstutz about 1 month ago. Updated 25 days ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
Docker
Target version:
Story points:
-
Release relationship:
Auto
Actions #1

Updated by Peter Amstutz about 1 month ago

  • Position changed from -941522 to -941514
  • Status changed from New to In Progress
Actions #2

Updated by Peter Amstutz about 1 month ago

Needed to install buildx, after that it builds, but now it is failing to push:

docker-arvbox: #5772

The issue seems to be this:

+ docker login -u arvados
Error: Cannot perform an interactive login from a non TTY device

It seems like it doesn't like our /home/jenkins/.dockercfg any more.

Actions #3

Updated by Brett Smith about 1 month ago

Peter Amstutz wrote in #note-2:

It seems like it doesn't like our /home/jenkins/.dockercfg any more.

https://docs.docker.com/reference/cli/docker/login/

Based on that, it seems like the preferred current name is ~/.docker/config.json. I tried that in docker-arvbox: #5773 but unfortunately got the same error. The logs show the file did get installed to the new location.

Other things to check:

  • Did the credentials coincidentally just expire?
  • The documentation says docker prefers to work with a credential store. I wonder if our new images, one way or another, now have one of these stores available, so docker is trying to use it and not finding anything there.
Actions #4

Updated by Brett Smith about 1 month ago

I did a docker login on my development machine and got config.json in a different format than we had it. Updated the Jenkins file to match and trying docker-arvbox: #5780

  • The documentation says docker prefers to work with a credential store. I wonder if our new images, one way or another, now have one of these stores available, so docker is trying to use it and not finding anything there.

Some basic testing suggests you need to set a configuration switch to get it to use a credential store so I doubt this is it.

Actions #5

Updated by Brett Smith about 1 month ago

Brett Smith wrote in #note-3:

  • Did the credentials coincidentally just expire?

This can't be it because the "credentials" are just base64-encoded username:password 🙄

Actions #6

Updated by Peter Amstutz about 1 month ago

  • Status changed from In Progress to Resolved
Actions #7

Updated by Peter Amstutz about 1 month ago

  • Assigned To changed from Peter Amstutz to Brett Smith
Actions #8

Updated by Peter Amstutz 25 days ago

  • Release set to 75
Actions

Also available in: Atom PDF