Skip to content

Builds with a pinned Docker label fail mysteriously #24

@blowery

Description

@blowery

When trying to build the original code in Automattic/wp-calypso#25321, dserve would bomb with the following log:

Time=2018-06-06T20:08:01.651Z | ---------------- DOCKER START ----------------
Time=2018-06-06T20:08:07.378Z | Step 1/16 : FROM node:8.11.2@sha256:321655aeb195b7946e9a29d28453388751389e8ced66b4dea772ae76a6985309
Time=2018-06-06T20:08:07.902Z | { status: 'Pulling from library/node', id: '8.11.2' }
Time=2018-06-06T20:08:08.182Z | Encountered error when building image

That PR was trying to pin the docker images to make builds more stable. Currently we're using labels from docker, which can change as the underlying OS takes patches.

Renovate (the new dependency updating tool) takes care of creating new PRs as the docker image associated with the label changes.

It's not critical that this get fixed (we decided to stick with plain labels, they've worked just fine so far), but it might be good to understand what went wrong.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions