I'm trying to connect to a docker host without TLS enabled, and Decking keeps giving me the following issue:
fs.js:500
return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
^
Error: ENOENT, no such file or directory '/path/to/ca.pem'
at Error (native)
at Object.fs.openSync (fs.js:500:18)
at Object.fs.readFileSync (fs.js:352:15)
at dockerConnection ($HOME\AppData\Roaming\npm\node_modules\decking\lib\decking.js:68:22)
at new Decking ($HOME\AppData\Roaming\npm\node_modules\decking\lib\decking.js:85:28)
at Object.<anonymous> ($HOME\AppData\Roaming\npm\node_modules\decking\bin\decking:15:15)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
Same problem with the other two files (key.pem and cert.pem). I just tried to put empty files in the path where it is looking for those files and then everything worked fine.A little workaround that I did was to put an IF in the lines of decking.json where the ca.pem and the other files are red. If the protocol parsed in the line above is HTTPS then decking would look for the permission files, if it is HTTP then decking won't look for them.
Why should we need to have certifications and keys even though we do not have TLS enabled?
I'm trying to connect to a docker host without TLS enabled, and Decking keeps giving me the following issue:
Same problem with the other two files (key.pem and cert.pem). I just tried to put empty files in the path where it is looking for those files and then everything worked fine.A little workaround that I did was to put an IF in the lines of decking.json where the ca.pem and the other files are red. If the protocol parsed in the line above is HTTPS then decking would look for the permission files, if it is HTTP then decking won't look for them.
Why should we need to have certifications and keys even though we do not have TLS enabled?
Thanks!