Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error parsing reference: "ubuntu:bionic as openbmc-base" is not a valid repository/tag #21

Open
geissonator opened this issue Oct 16, 2018 · 5 comments
Assignees

Comments

@geissonator
Copy link
Contributor

We're getting this on our x86 based CI machines. It works ok on our POWER based CI system so no idea what's going on yet:

https://openpower.xyz/job/openbmc-repository-ci/

12:26:47 + docker build --network=host -t openbmc/ubuntu-unit-test -
12:26:47 Sending build context to Docker daemon 9.728 kB

12:26:47 Step 1/67 : FROM ubuntu:bionic as openbmc-base
12:26:47 Error parsing reference: "ubuntu:bionic as openbmc-base" is not a valid repository/tag: invalid reference format
12:26:47 ++ cleanup
12:26:47 ++ local status=1
12:26:47 ++ '[' -n /tmp/tmp.3hfpsTLe0x ']'
12:26:47 ++ rm -f /tmp/tmp.3hfpsTLe0x
12:26:47 ++ trap - EXIT ERR
12:26:47 ++ exit 1
@geissonator
Copy link
Contributor Author

For now I've just changed the jenkins CI job to only use the POWER system. This seems like maybe a docker version thing?

POWER:

docker --version
Docker version 17.06.0-ce, build 411dd6e

x86:

docker --version
Docker version 1.13.1, build 092cba3

That seems ridiculously old... I'll see if I can update it.

@geissonator geissonator self-assigned this Oct 16, 2018
@wak-google
Copy link
Contributor

Yeah, I believe the AS part of the FROM line was added in a 2017 version. 2017.06 must have it because the tests pass sometimes.

@geissonator
Copy link
Contributor Author

Darn, got the x86 systems updated but ending up with this version which does not work:

 docker --version
Docker version 17.03.2-ce, build f5ec1e2

Will need to look into manually updating my ubuntu links to get more recent.

@wak-google
Copy link
Contributor

Is this coming from the upstream docker repos?

@geissonator
Copy link
Contributor Author

Updating docker seemed to fix this for the most part, still reports of an intermittent issue that appears related to moby/moby#33974

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants