docker pull nodered/node-red fails with DOCKER_CONTENT_TRUST=1

Open
#220 6 comments 0 reactions 1 assignee View on GitHub

@hardillb is already working on this.

Since Jun 1, 2021.

Assessment

This issue has not been assessed yet.

Description

What are the steps to reproduce?
DOCKER_CONTENT_TRUST=1 docker pull nodered/node-red
What happens?
[root@fitlet-2 tpm2]# docker pull nodered/node-red
Using default tag: latest
Error: remote trust data does not exist for docker.io/nodered/node-red: notary.docker.io does not have trust data for docker.io/nodered/node-red
What do you expect to happen?
[root@fitlet-2 tpm2]# docker pull nodered/node-red
Using default tag: latest
latest: Pulling from nodered/node-red
0a6724ff3fcd: Downloading  147.1kB/2.815MB
0e88ccee218e: Downloading  4.135MB/22.2MB
68aee5547ce7: Downloading  1.932MB/2.345MB
449ce1354b7e: Waiting
ef5a64ae34b5: Waiting
ce7315e3679c: Waiting
14134559e7be: Waiting
37cbffb78fc3: Waiting
985420e950d0: Waiting
241e4876a223: Waiting
6eb8914161d7: Waiting
9974816a3be8: Waiting
Please tell us about your environment:
  • Node-RED version: nodered/node-red:latest
  • Node.js version: included in Docker image
  • npm version: included in Docker Image
  • Platform/OS: Docker, Fedora IoT 33
  • Browser: Chrome

Workaround:

[root@fitlet-2 tpm2]# DOCKER_CONTENT_TRUST=0 docker pull nodered/node-red
Dominant language
Shell
Stars
540
Forks
434
Avg merge
24m
Merged PRs (30d)
5

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from node-red/node-red-docker

All issues in node-red/node-red-docker

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.