From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: Benedikt Niedermayr <benbrenson89@googlemail.com>,
isar-users@googlegroups.com
Subject: Re: Adding additional apt repositories during the build
Date: Fri, 9 Nov 2018 13:53:31 +0300 [thread overview]
Message-ID: <f0faf827-8204-8bd7-b24a-b47905f849e9@ilbers.de> (raw)
In-Reply-To: <42954dda-cc28-4cf4-e1fe-a3b1b636a4a3@googlemail.com>
Hi Benedikt,
On 11/9/18 1:17 PM, 'Benedikt Niedermayr' via isar-users wrote:
> Hi guys,
>
> I wanted to add additional repositories at the beginning of the build
> (e.g for installing docker-ce) and I tried to add it to the
> "DISTRO_APT_KEYS" variable.
>
> But doing that way debootstrap doesn't seem to work anymore:
>
> | I: Retrieving InRelease
> | I: Retrieving Release
> | I: Retrieving Release.gpg
> | I: Checking Release signature
> | E: Release signed by unknown key (key id EF0F382A1A7B6500)
> | WARNING: exit code 1 from a shell command.
>
>
> I think the default gpg keyring gets overwritten.
>
> Do you have any proposals or clean solutions for this?
Yes, this is a known problem (I absolutely agree that this
DISTRO_APT_KEYS is confusing) and I plan to fix it in a next couple of
weeks.
Thanks for your proposal - I'll think if installation of keys could be
done with less "hooky" way.
Regards,
Maxim.
>
> For now I implemented a little hack to get things to work.
>
> Maybe we need a functionality in Isar which works like a hook based
> mechanism, so we can add those
>
> to the initial build step when bootstrapping the rootfs.
>
>
> isar-bootstrap-host.bbappend & isar-bootstrap-target.bbappend:
>
> do_bootstrap_append() {
> sudo install -v -m755 ${WORKDIR}/custom-setup.sh ${ROOTFSDIR}/
> sudo flock "${ISAR_BOOTSTRAP_LOCK}"-c "\
> set -e
> export DISTRO_SUITE="${@get_distro_suite(d, True)}"
> export DISTRO_ARCH="${DISTRO_ARCH}"
> chroot "${ROOTFSDIR}" /custom-setup.sh
> "
> sudo rm -f ${ROOTFSDIR}/custom-setup.sh
> }
> custom-setup.sh:
> GPG_URL="https://download.docker.com/linux/debian/gpg"
> apt-get install --no-install-recommends -y curl apt-transport-https
> ca-certificates curl gnupg2 software-properties-common
> curl -fsSL $GPG_URL |apt-key add -
> echo "deb [arch=$DISTRO_ARCH] https://download.docker.com/linux/debian \
> $DISTRO_SUITE stable"|\
> tee /etc/apt/sources.list.d/docker.list
> apt-get update -y
> Regards
> Benedikt
>
> --
> You received this message because you are subscribed to the Google
> Groups "isar-users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to isar-users+unsubscribe@googlegroups.com
> <mailto:isar-users+unsubscribe@googlegroups.com>.
> To post to this group, send email to isar-users@googlegroups.com
> <mailto:isar-users@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/isar-users/42954dda-cc28-4cf4-e1fe-a3b1b636a4a3%40googlemail.com
> <https://groups.google.com/d/msgid/isar-users/42954dda-cc28-4cf4-e1fe-a3b1b636a4a3%40googlemail.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.
--
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
prev parent reply other threads:[~2018-11-09 10:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 10:17 Benedikt Niedermayr
2018-11-09 10:53 ` Maxim Yu. Osipov [this message]
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=f0faf827-8204-8bd7-b24a-b47905f849e9@ilbers.de \
--to=mosipov@ilbers.de \
--cc=benbrenson89@googlemail.com \
--cc=isar-users@googlegroups.com \
/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