From: Andreas Reichel <andreas.reichel.ext@siemens.com>
To: isar-users@googlegroups.com
Subject: Additional debian repo with different pgp key
Date: Fri, 15 Feb 2019 16:16:10 +0100 [thread overview]
Message-ID: <20190215151608.GA5175@iiotirae> (raw)
Hi,
I have a problem with using a separate docker repository together with
its key.
As far as I understood it, I have to do the following:
1st, create a list file which mentions the docker repository:
So I created a docker-stretch.list, where I have the line
----
deb http://download.docker.com/linux/debian stretch stable
----
This file is added via
----
DISTRO_APT_SOURCES_append = " conf/distro/docker-stretch.list"
----
which is working.
Then I add the `docker-ce` package to `IMAGE_PREINSTALL` which does not
work because the package is untrusted. Therefore I have to import the
pgp key, which I should be able to do with
2nd: add the key to apt keys:
----
DISTRO_APT_KEYS_append = " https://download.docker.com/linux/debian/gpg;sha256sum=1500c1f56fa9e26b9b8f42452a553675796ade0807cdce11975eb98170b3a570"
----
However, then I get the following error:
----
| DEBUG: Executing shell function do_generate_keyring
| gpg: WARNING: unsafe permissions on homedir '/build/build/downloads'
| gpg: keybox '/build/build/tmp/work/debian-stretch-arm64/isar-bootstrap-target/apt-keyring.gpg' created
| gpg: can't open '/build/build/tmp/work/debian-stretch-arm64/isar-bootstrap-target/linux/debian/gpg': No such file or directory
| gpg: Total number processed: 0
| WARNING: exit code 2 from a shell command.
----
It seems, that the last part of the URL is appended to the working
directory. But the resulting directory does not exist. What is the
intended course of action for this standard scenario to use another
debian repo for image building?
Last patch I saw on next was about local keys. But standard should be
remote keys with URI I think, because every repo that needs one should
provide one this way... am I wrong?
vG
Andreas
--
Andreas Reichel
Dipl.-Phys. (Univ.)
Software Consultant
Andreas.Reichel@tngtech.com, +49-174-3180074
TNG Technology Consulting GmbH, Betastr. 13a, 85774 Unterfoehring
Geschaeftsfuehrer: Henrik Klagges, Dr. Robert Dahlke, Gerhard Mueller
Sitz: Unterfoehring * Amtsgericht Muenchen * HRB 135082
next reply other threads:[~2019-02-15 15:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 15:16 Andreas Reichel [this message]
2019-02-19 15:29 ` Henning Schild
2019-02-20 11:21 ` [PATCH 0/1] Fix remote key fetching apt keyring Andreas J. Reichel
2019-02-20 11:21 ` [PATCH 1/1] Fix path to user gpg-keys Andreas J. Reichel
2019-02-20 11:27 ` [PATCH 0/1] Fix remote key fetching apt keyring Jan Kiszka
2019-02-20 11:36 ` Andreas Reichel
2019-02-20 11:47 ` Andreas Reichel
2019-02-20 11:58 ` Maxim Yu. Osipov
2019-02-20 14:45 ` Andreas Reichel
2019-02-20 12:36 ` Henning Schild
2019-02-20 12:52 ` Additional debian repo with different pgp key Maxim Yu. Osipov
2019-02-26 12:39 ` Andreas Reichel
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=20190215151608.GA5175@iiotirae \
--to=andreas.reichel.ext@siemens.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