Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/5] support/docker: add an Arch image
Date: Mon, 16 Jul 2018 18:15:31 +0200	[thread overview]
Message-ID: <20180716161531.GA5141@scaer> (raw)
In-Reply-To: <CAFGQKxfOSY5-eaNrYpuegD8X6CF6shbdZzusY1E8fWUvJcFm4w@mail.gmail.com>

Martin, All,

On 2018-07-16 01:13 +0100, Martin Bark spake thusly:
> On 15 July 2018 at 20:45, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > On 2018-07-15 20:30 +0100, Martin Bark spake thusly:
> >> On 15 July 2018 at 10:05, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > [--SNIP--]
> >> > So, the reasoning is that, since we use a pinned version of the
> >> > repository, running "pacman -Sy --noconfirm" will always yield the same
> >> > state of the distribution.
> >> >
> >> > Now, it happens that we need to add a new package to the image, e.g. for
> >> > local testing. We can thus re-use the intermediate, locally-cached image
> >> > that has the local repository updated.
> >> >
> >> > It kinda speeds up things a bit.
[--SNIP--]
> hey! here's how you can make it reproducible

Wee! :-)

> 1) build the alpine docker image.
> 2) mkdir -p support/docker/alpine_snapshot
> 3) docker run -it --rm -v
> $PWD/support/docker/alpine_snapshot:/snapshot -u root
> buildroot/alpine-3.7:$BR2_DOCKER_VERSION bash
> 4) inside the container run
> 
> mkdir -p /var/cache/apk
> ln -s /var/cache/apk /etc/apk/cache
> apk cache sync
> cp -a /etc/apk/cache/*.apk /snapshot
> exit
> 
> 7) sudo chown -R $(id -u):$(id -g) support/docker/alpine_snapshot
> 6) edit the Dockerfile so it looks like this
> 
> COPY ./alpine_snapshot /snapshot
> RUN apk add /snapshot/*.apk
> 
> 7) build the alpine docker image again.  it will build using the apk
> files from /snapshot directory we just created
> 
> This is not ideal but it's a proof of concept.  To improve you could
> copy the apk to a website, setup it up as a proper signed package
> repository and then edit /etc/apk/repositories to use this snapshot

Wooo... Scary...

OK, I'll give it a try.

Thanks you for the feedback! :-)

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2018-07-16 16:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-13  6:38 [Buildroot] [PATCH 0/5] support/docker: add new dockers Yann E. MORIN
2018-07-13  6:38 ` [Buildroot] [PATCH 1/5] core: add a rule to generate all our docker images Yann E. MORIN
2018-07-16  0:39   ` Ricardo Martincoski
2018-07-13  6:38 ` [Buildroot] [PATCH 2/5] support/docker: rename the Dockerfile and its accompanying file Yann E. MORIN
2018-07-16  0:44   ` Ricardo Martincoski
2018-07-13  6:38 ` [Buildroot] [PATCH 3/5] support/docker: add a Fedore-28 based image Yann E. MORIN
2018-07-16  0:48   ` Ricardo Martincoski
2018-07-13  6:38 ` [Buildroot] [PATCH 4/5] support/docker: add an Arch image Yann E. MORIN
2018-07-14 11:19   ` Martin Bark
2018-07-14 12:01     ` Yann E. MORIN
2018-07-15  9:05       ` Yann E. MORIN
2018-07-15 19:30         ` Martin Bark
2018-07-15 19:45           ` Yann E. MORIN
2018-07-16  0:13             ` Martin Bark
2018-07-16 16:15               ` Yann E. MORIN [this message]
2018-07-13  6:38 ` [Buildroot] [PATCH 5/5] support/docker: add an Alpine-3.7 based image Yann E. MORIN
2018-07-14 11:19   ` Martin Bark
2018-07-16  1:05   ` Ricardo Martincoski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180716161531.GA5141@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox