pokusio / pokus-notary

A POC on using Notary to manage Content Trust
0 stars 0 forks source link

todo #1

Open Jean-Baptiste-Lasselle opened 4 years ago

Jean-Baptiste-Lasselle commented 4 years ago

Complete all doc study starting at https://docs.docker.com/notary/getting_started/

Jean-Baptiste-Lasselle commented 4 years ago

# provisioning with git clone and docker-compose up -d works, even if we can read
# some errors in the logs
jbl@pegasusio:~/notary$ docker exec -it notary_signer_1 sh -c "cat fixtures/signer-config.json"
{
    "server": {
        "grpc_addr": ":7899",
        "tls_cert_file": "./notary-signer.crt",
        "tls_key_file": "./notary-signer.key",
        "client_ca_file": "./notary-server.crt"
    },
    "logging": {
        "level": "debug"
    },
    "storage": {
        "backend": "mysql",
        "db_url": "signer@tcp(mysql:3306)/notarysigner?parseTime=True"
    }
}
jbl@pegasusio:~/notary$ docker exec -it notary_server_1 sh -c "cat fixtures/signer-config.json"
{
    "server": {
        "grpc_addr": ":7899",
        "tls_cert_file": "./notary-signer.crt",
        "tls_key_file": "./notary-signer.key",
        "client_ca_file": "./notary-server.crt"
    },
    "logging": {
        "level": "debug"
    },
    "storage": {
        "backend": "mysql",
        "db_url": "signer@tcp(mysql:3306)/notarysigner?parseTime=True"
    }
}
jbl@pegasusio:~/notary$ docker exec -it notary_server_1 sh -c "whoami && ps aux"
root
PID   USER     TIME  COMMAND
    1 root      0:00 notary-server -config=fixtures/server-config.json
   32 root      0:00 ps aux
jbl@pegasusio:~/notary$ docker exec -it notary_signer_1 sh -c "whoami && ps aux"
root
PID   USER     TIME  COMMAND
    1 root      0:00 notary-signer -config=fixtures/signer-config.json
   54 root      0:00 ps aux
jbl@pegasusio:~/notary$ 

When interacting with Docker Hub repositories, you must instruct the client to use the associated trust directory, which by default is found at ~/.docker/trust within the calling user’s home directory