You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm seeing some activation failures, ~.1% failure rate. The overwhelming majority of these failures happen on Windows but there are results for both Linux and Mac.
Error: ENOENT: no such file or directory, open '<REDACTED: user-file-path>'
Stack: Object.openSync fs.js:447:3\nObject.func asar.js:140:31\nObject.func [as openSync] asar.js:140:31
The text was updated successfully, but these errors were encountered:
I have a theory. The error is not really new, but it used to happen during context init, now happens during activation. The constructor for Dockerode also used to be in context init but is now in activation.
If DOCKER_CERT_PATH is set, docker-modem tries to open ca.pem, cert.pem, and key.pem. This will fail with the error message we see. Additionally, nearly all instances of this error have a host source of env, strengthening this theory.
What I'm not sure about is why almost all of the errors happen on Windows. 🤷
I'm seeing some activation failures, ~.1% failure rate. The overwhelming majority of these failures happen on Windows but there are results for both Linux and Mac.
Error: ENOENT: no such file or directory, open '<REDACTED: user-file-path>'
Stack: Object.openSync fs.js:447:3\nObject.func asar.js:140:31\nObject.func [as openSync] asar.js:140:31
The text was updated successfully, but these errors were encountered: