-
e2e tests with `make -f docker.Makefile test` fail on branches `18.06`,`18.09`,`19.03` clean from this repo. I suspect there is some undocumented setup needed for the e2e tests.
Assertion failed er…
-
Running notary on a GUN that contains a port number (e.g. the 443 in docker.io:443/library/ubuntu) on Windows fails because the colon is an invalid character in a directory name:
```
notary -v -D …
-
It would be useful to support multiple notary servers (ex: official Docker hub server + private notary server) without having to prefix each command with `DOCKER_CONTENT_TRUST_SERVER` to docker or dif…
-
$ export DOCKER_CONTENT_TRUST=1
$ docker pull adoptopenjdk/openjdk11:alpine-jre
Error: remote trust data does not exist for docker.io/adoptopenjdk/openjdk11: notary.docker.io does not have trust dat…
-
**Describe the bug**
The connaisseur MutatingWebhook is throwing a 401 error when trying to verify a signed image during pod deployment. See "Optional: To reproduce" for more information.
**Expect…
-
Dear all,
I tried to automate this via jenkins . Basically, I exported my passphrase + exported the notary into the /etc/profile and ran jenkins. My jenkins is reading from a github repo where my …
-
I was doing some tests to start enforcing Docker Content Trust (DCT) in my pipeline and found that the last signed tag is 6 months old (alpine:3.12.1)
Also, since the alpine:3 is signed, you can wr…
-
* [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
-
The current use of notary integrated in the docker(1) CLI (as of 1.8.2) is ineffective in automated setups where Docker is driven using the Remote API without going through the CLI.
Currently, automa…
-
Has anybody considered the idea of a implementing a notary client daemon similar to the Docker daemon? In efforts to bring automation to notary and have tagging keys dynamically generated upon new re…