Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions Dockerfile
Original file line number Diff line number Diff line change
@@ -1,8 +1,7 @@
# this container builds the kilt-parachain binary from source files and the runtime library
# pinned the version to avoid build cache invalidation

# c4f0daf3-20220110 -> rust version rustc 1.58.0-nightly (46b8e7488 2021-11-07)
FROM paritytech/ci-linux:f203f298-20220421 as builder
FROM docker.io/paritytech/ci-linux:production as builder

@wischli wischli Jun 9, 2022

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I fear that the production image will be bumped up by Parity while we want to have full control over bumping the image to reduce error likelihood when building.

I suggest to stay with a distinct hash. The one suggested has the same digest as the current production one, e.g., they are the same.

Suggested change
FROM docker.io/paritytech/ci-linux:production as builder
FROM paritytech/ci-linux:eb1f6a26-20220518

@ggera ggera Jun 10, 2022

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup, I was kinda puzzled. Since the toolchain file has precedence over the docker image, we kinda have no control.


WORKDIR /build

Expand Down