- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If I try to build this dockerfile
FROM intel/oneapi-hpckit:latest
RUN apt update \
&& apt -y install \
cmake \
&& apt clean
The apt update step fails
: docker build -t test -f Dockerfile .
[+] Building 141.1s (5/5) FINISHED docker:desktop-linux
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 143B 0.0s
=> [internal] load metadata for docker.io/intel/oneapi-hpckit:latest 1.1s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 182B 0.0s
=> [1/2] FROM docker.io/intel/oneapi-hpckit:latest@sha256:8fd25f1450656af2ff791a35bdb4330e24d91f424bafd7d55818aec44bdd5ef0 133.2s
=> => resolve docker.io/intel/oneapi-hpckit:latest@sha256:8fd25f1450656af2ff791a35bdb4330e24d91f424bafd7d55818aec44bdd5ef0 0.0s
=> => sha256:d4ada6edccfb8e6a0104c44010db98a1d65e990d3256329f4cf9ac90cd54b8f3 21.18kB / 21.18kB 0.0s
=> => sha256:8fd25f1450656af2ff791a35bdb4330e24d91f424bafd7d55818aec44bdd5ef0 2.20kB / 2.20kB 0.0s
=> => sha256:e1ca900d72e4f22cca0f6a25e284529d6a198e56a040a05d8665823ec897fd1e 23.70kB / 23.70kB 0.3s
=> => sha256:77988f474497da3022d30f8a28ef31e4e155acd7d7b28670f0a195d89d8b4cec 44.02MB / 44.02MB 1.6s
=> => sha256:3dd181f9be599de628e1bc6d868d517125e07f968824bcf7b7ed8d28ad1026b1 30.45MB / 30.45MB 0.8s
=> => sha256:e620657ebe448e4f72c8d468377ec585359b7312568f764c99bde904e4af622f 3.20kB / 3.20kB 0.4s
=> => sha256:73901b5c50b77e1222e789f2b69432a006ac29652af436cf148c02944982d7e0 275B / 275B 0.8s
=> => sha256:6c83bbaffcf8722188d1afc564c5f87504ab14667e6046bb16697bf2f96eb2cb 355B / 355B 0.9s
=> => extracting sha256:3dd181f9be599de628e1bc6d868d517125e07f968824bcf7b7ed8d28ad1026b1 0.7s
=> => sha256:57423049948f7b4f634e6ada303b779357dbc0b39454d2887a08be5a15b4a3e2 1.47kB / 1.47kB 1.0s
=> => sha256:3401b0a38f2bc9c0f416a24f24582d41c248ad4535d7e9762ce05fb31971da1c 4.77GB / 4.77GB 67.5s
=> => sha256:8dc5935d8d8bb5f75eb2962c30cf0c9c5aace4174b3d1ed45f140211d9a855da 288B / 288B 1.0s
=> => extracting sha256:e1ca900d72e4f22cca0f6a25e284529d6a198e56a040a05d8665823ec897fd1e 0.0s
=> => extracting sha256:77988f474497da3022d30f8a28ef31e4e155acd7d7b28670f0a195d89d8b4cec 1.1s
=> => extracting sha256:e620657ebe448e4f72c8d468377ec585359b7312568f764c99bde904e4af622f 0.0s
=> => extracting sha256:73901b5c50b77e1222e789f2b69432a006ac29652af436cf148c02944982d7e0 0.0s
=> => extracting sha256:6c83bbaffcf8722188d1afc564c5f87504ab14667e6046bb16697bf2f96eb2cb 0.0s
=> => extracting sha256:57423049948f7b4f634e6ada303b779357dbc0b39454d2887a08be5a15b4a3e2 0.0s
=> => extracting sha256:8dc5935d8d8bb5f75eb2962c30cf0c9c5aace4174b3d1ed45f140211d9a855da 0.0s
=> => extracting sha256:3401b0a38f2bc9c0f416a24f24582d41c248ad4535d7e9762ce05fb31971da1c 64.7s
=> ERROR [2/2] RUN apt update && apt -y install cmake && apt clean 6.7s
------
> [2/2] RUN apt update && apt -y install cmake && apt clean:
0.204
0.204 WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
0.204
0.566 Get:1 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
0.602 Get:2 https://apt.repos.intel.com/oneapi all InRelease [5676 B]
0.682 Get:3 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB]
0.848 Get:4 https://repositories.intel.com/gpu/ubuntu jammy InRelease [15.4 kB]
1.171 Get:5 https://apt.repos.intel.com/oneapi all/main all Packages [146 kB]
1.310 Get:6 https://apt.repos.intel.com/oneapi all/main amd64 Packages [508 kB]
1.365 Get:7 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB]
1.524 Get:8 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [109 kB]
1.931 Get:9 http://security.ubuntu.com/ubuntu jammy-security/restricted amd64 Packages [2395 kB]
2.290 Get:10 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages [1853 kB]
2.302 Err:4 https://repositories.intel.com/gpu/ubuntu jammy InRelease
2.302 The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 28DA432DAAC8BAEA
2.326 Get:11 http://security.ubuntu.com/ubuntu jammy-security/multiverse amd64 Packages [44.7 kB]
2.327 Get:12 http://security.ubuntu.com/ubuntu jammy-security/universe amd64 Packages [1083 kB]
3.150 Get:13 http://archive.ubuntu.com/ubuntu jammy/restricted amd64 Packages [164 kB]
3.325 Get:14 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages [1792 kB]
3.698 Get:15 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages [17.5 MB]
4.447 Get:16 http://archive.ubuntu.com/ubuntu jammy/multiverse amd64 Packages [266 kB]
4.574 Get:17 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [2125 kB]
4.607 Get:18 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages [2468 kB]
4.728 Get:19 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [1375 kB]
4.744 Get:20 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 Packages [51.1 kB]
4.990 Get:21 http://archive.ubuntu.com/ubuntu jammy-backports/main amd64 Packages [81.0 kB]
5.447 Get:22 http://archive.ubuntu.com/ubuntu jammy-backports/universe amd64 Packages [31.9 kB]
5.653 Reading package lists...
6.369 W: GPG error: https://repositories.intel.com/gpu/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 28DA432DAAC8BAEA
6.369 E: The repository 'https://repositories.intel.com/gpu/ubuntu jammy InRelease' is not signed.
------
Dockerfile:3
--------------------
2 |
3 | >>> RUN apt update \
4 | >>> && apt -y install \
5 | >>> cmake \
6 | >>> && apt clean
7 |
--------------------
ERROR: failed to solve: process "/bin/sh -c apt update && apt -y install cmake && apt clean" did not complete successfully: exit code: 100
There seem to be another user with a similar issue.
I've tried adding the key explicitly
FROM intel/oneapi-hpckit:latest
RUN curl https://yum.repos.intel.com/intel-gpg-keys/GPG-PUB-KEY-INTEL-SW-PRODUCTS-2023.PUB | apt-key add -
RUN apt update \
&& apt -y install \
cmake \
&& apt clean
but I get the same error. What am I missing and how can I fix this?
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I tried the instructions here, and I still get the same thing:
FROM intel/oneapi-hpckit:latest
RUN wget -qO - https://repositories.intel.com/gpu/intel-graphics.key | gpg --yes --dearmor --output /usr/share/keyrings/intel-graphics.gpg
RUN apt update
4.876 Get:21 http://archive.ubuntu.com/ubuntu jammy-backports/main amd64 Packages [110 kB]
5.402 Get:22 http://archive.ubuntu.com/ubuntu jammy-backports/universe amd64 Packages [35.0 kB]
5.530 Reading package lists...
6.339 W: GPG error: https://repositories.intel.com/gpu/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 28DA432DAAC8BAEA
6.339 E: The repository 'https://repositories.intel.com/gpu/ubuntu jammy InRelease' is not signed.
------
Dockerfile.intel:6
--------------------
4 | RUN wget -qO - https://repositories.intel.com/gpu/intel-graphics.key | gpg --yes --dearmor --output /usr/share/keyrings/intel-graphics.gpg
5 |
6 | >>> RUN apt update
7 |
8 | # RUN apt update \
--------------------
ERROR: failed to solve: process "/bin/sh -c apt update" did not complete successfully: exit code: 100
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There seems to be an error in the docs.
Instead of
RUN wget -qO - https://repositories.intel.com/gpu/intel-graphics.key | \
gpg --yes --dearmor --output /usr/share/keyrings/intel-graphics.gpg
use:
RUN wget -qO - https://repositories.intel.com/gpu/intel-graphics.key | \
gpg --yes --dearmor --output /usr/share/keyrings/intel-graphics-archive-keyring.gpg
The gpg file name needs to be in sync with the content of /etc/apt/sources.list.d/intel-graphics.list
deb [signed-by=/usr/share/keyrings/intel-graphics-archive-keyring.gpg arch=amd64] https://repositories.intel.com/gpu/ubuntu jammy unified
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That worked but for the past several months (year?) I haven't ever needed something like this in the dockerfile. Is this something that needs to be permanent now?

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page