did:dock examples not resolving

[mike-parkhill]

We have made changes to the did:dock driver that require the latest Docker image to be pulled.

How do we initiate a container refresh?

[BernhardFuchs]

The images get pulled everytime a deployment is started but atm there is no option to trigger that for contributors. Best way is to create an issue or a PR if a file is changed and then we do a restart of the driver.

We had a few deployments today as we are testing a new driver, so your latest image is deployed by now. I tried the example DIDs and did:dock:5EAp6DB2pkKuAfbhQiqAXFY4XPZkJrvtWKad4ChDmWwDrC8n (2nd one in the list) throws following error:

[notFound] 404 Not Found ({"error":"NoDIDError: A DID document lookup was successful, but the DID in question does not exist. This is different from a network error."})

Logs from driver are:

yarn run v1.22.5
warning package.json: License should be a valid SPDX license expression
$ npx babel-node index.js
Dock DID driver running on port 8080
Connecting to node...
Connecting to node...
Connecting to node...
Connecting to node...
Connecting to node...
Connecting to node...
Connecting to node...
Connecting to node...
Connecting to node...
Connecting to node...
Connecting to node...
Connecting to node...
2022-10-04 13:21:51        REGISTRY: Unknown signed extensions OnlyMigrator found, treating them as no-effect
Connected to node, ready to serve DIDs!
2022-10-04 13:21:54        REGISTRY: Unknown signed extensions OnlyMigrator found, treating them as no-effect
Connected to node, ready to serve DIDs!
2022-10-04 13:21:56        REGISTRY: Unknown signed extensions OnlyMigrator found, treating them as no-effect
Connected to node, ready to serve DIDs!
2022-10-04 13:21:58        REGISTRY: Unknown signed extensions OnlyMigrator found, treating them as no-effect
Connected to node, ready to serve DIDs!
2022-10-04 13:22:00        REGISTRY: Unknown signed extensions OnlyMigrator found, treating them as no-effect
Connected to node, ready to serve DIDs!
2022-10-04 13:22:02        REGISTRY: Unknown signed extensions OnlyMigrator found, treating them as no-effect
Connected to node, ready to serve DIDs!
2022-10-04 13:22:03        REGISTRY: Unknown signed extensions OnlyMigrator found, treating them as no-effect
Connected to node, ready to serve DIDs!
2022-10-04 13:22:04        REGISTRY: Unknown signed extensions OnlyMigrator found, treating them as no-effect
Connected to node, ready to serve DIDs!
2022-10-04 13:22:07        REGISTRY: Unknown signed extensions OnlyMigrator found, treating them as no-effect
Connected to node, ready to serve DIDs!
2022-10-04 13:22:08        REGISTRY: Unknown signed extensions OnlyMigrator found, treating them as no-effect
Connected to node, ready to serve DIDs!
2022-10-04 13:22:09        REGISTRY: Unknown signed extensions OnlyMigrator found, treating them as no-effect
Connected to node, ready to serve DIDs!
2022-10-04 13:22:11        REGISTRY: Unknown signed extensions OnlyMigrator found, treating them as no-effect
Connected to node, ready to serve DIDs!

[cykoder]

@BernhardFuchs i think that DID just doesnt exist on the chain anymore, the other two examples are working for me:

did:dock:5CxUdCGtopZEJhdv6kfLBZ22PMZX7UK8mdcHbTVw2nw6MVZH

did:dock:5CDsD8HZa6TeSfgmMcxAkbSXYWeob4jFQmtU6sxr4XWTZzUA

[peacekeeper]

Hello @SamHellawell I think it would be best if you could also update this file in your PR with the updated examples that you would like people to use:

https://github.com/decentralized-identity/universal-resolver/blob/main/uni-resolver-web/src/main/resources/application.yml#L213

[cykoder]

@peacekeeper Yep was getting around to that, here's the PR: https://github.com/decentralized-identity/universal-resolver/pull/325

Was looking at just registering it again but probably makes sense to stick with 2 throughout (even on our Github readme).

[peacekeeper]

@SamHellawell I think we can close this, do you agree?

[cykoder]

@peacekeeper yep seems good to close to me, dock dids have been resolving properly for a little bit now