You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# SOURCE_DATE_EPOCH is set to 1691114774 (i.e., 20230804T020614Z, timestamp of /etc/apt/sources.list)FROM ubuntu:jammy-20230804
ENV DEBIAN_FRONTEND=noninteractive
RUN \
--mount=type=cache,target=/var/cache/apt,sharing=locked \
--mount=type=cache,target=/var/lib/apt,sharing=locked \
--mount=type=bind,source=./repro-sources-list.sh,target=/usr/local/bin/repro-sources-list.sh \ # <-- THIS LINE HERE
repro-sources-list.sh && \
apt-get update && \
apt-get install -y gcc
What do you think about showing an example Dockerfile that fetches /repro-sources-list.sh?
I'm thinking this repo could be maintaining a docker image that only contains the script in a scratch image. This could make the setup even simpler:
# SOURCE_DATE_EPOCH is set to 1691114774 (i.e., 20230804T020614Z, timestamp of /etc/apt/sources.list)FROM ubuntu:jammy-20230804
ENV DEBIAN_FRONTEND=noninteractive
RUN \
--mount=type=cache,target=/var/cache/apt,sharing=locked \
--mount=type=cache,target=/var/lib/apt,sharing=locked \
--mount=from=reproducible-containers/repro-sources-list.sh:v1@sha256:...,type=bind,source=/repro-sources-list.sh,target=/usr/local/bin/repro-sources-list.sh \ # <-- THIS LINE HERE
repro-sources-list.sh && \
apt-get update && \
apt-get install -y gcc
The scratch image Dockerfile could be:
# Tag as reproducible-containers/repro-sources-list.sh:v1FROM scratch
COPY ./repro-sources-list.sh /
Thoughts?
The text was updated successfully, but these errors were encountered:
Hi! Thanks for your great work :)
The README mentions
What do you think about showing an example
Dockerfile
that fetches/repro-sources-list.sh
?I'm thinking this repo could be maintaining a docker image that only contains the script in a
scratch
image. This could make the setup even simpler:The scratch image
Dockerfile
could be:Thoughts?
The text was updated successfully, but these errors were encountered: