-
There's no reason to run scanner adapter service as root in the Docker container. We should update the Dockerfile respectively.
```
$ dockle docker.io/goharbor/harbor-scanner-clair:1.0.1-rc1
WARN…
-
* [x] This is a bug report
* [ ] This is a feature request
* [x] I searched existing issues before opening this one
### Expected behavior
Successfully pull signed images with content tru…
wu105 updated
3 years ago
-
### What is not working as expected?
When verifying the signed container image with notation I am getting the error
### What did you expect to happen?
I just test notation for a new build image and…
-
We currently use custom shell script with `expect` and other assorted hacks to push manifest lists and sign them. While `docker manifest push` currently does not work with `DOCKER_CONTENT_TRUST=1` (se…
-
Docker Content Trust currently parses Dockerfiles client-side to resolve the image-digest for all images that are used.
However, with the addition of multi-stage builds, and dynamically changing th…
-
It seems that something is wrong with signing base Node images' tags on Docker Hub:
$ DOCKER_CONTENT_TRUST=1 docker pull node
Using default tag: latest
Pull (1 of 1): node:latest@sha2…
-
I am using Jenkins Slave machines to sign and push docker images.
I have root-ca crt in the slave machines.
export DOCKER_CONTENT_TRUST=1
export DOCKER_CONTENT_TRUST_SERVER= https://personal-serve…
-
### Summary
`spack buildcache push` **always** creates new tarballs from install prefixes of specs to be pushed.
This is problematic because it's
1. inefficient when pushing the same spec to …
-
Context:
\[1\] [Jupyter Forum: Jupyterlab not remembering trust for notebooks](https://discourse.jupyter.org/t/jupyterlab-not-remembering-trust-for-notebooks/7869/5)
\[2\] [Jupyter Forum: SVG eith…
-
$ alias dockernotary="notary -c $HOME/.docker/trust/config.json -d $HOME/.docker/trust/ -s https://notary.docker.io"
$ dockernotary version
notary
Version: 0.4.3
Git commit: 9211198
$ dock…