ERROR: balena deploy

sergg@nodejs:~/client$ balena deploy novikov_dev --logs --source . --emulated
Debug: original argv0=“balena” argv=[/usr/lib/balena-cli/balena,/snapshot/balena-cli/bin/balena,deploy,novikov_dev,–logs,–source,., --emulated] length=8
[Debug] Parsing input…
[Debug] Loading project…
[Debug] Resolving project…
[Debug] Failed to resolve project:
[Debug] AggregateError of:
[Debug] Error: ENOENT: no such file or directory, open ‘/home/sergg/client/docker-compose.yml’
[Debug] Error: ENOENT: no such file or directory, open ‘/home/sergg/client/docker-compose.yaml’
[Info] Creating default composition with source: /home/sergg/client
[Debug] Creating project…
[Info] Everything is up to date (use --build to force a rebuild)
[Info] Creating release…
[Debug] Tagging images…
[Debug] Authorizing push…
[Info] Pushing images to registry…
Retrying “registry.balena.ihost.net.ua/v2/c6fc9e5173e5db367cb5766323c575e9:latest” after 2.00s (1 of 3) due to: Error: Get https://re gistry.balena.ihost.net.ua/v2/: x509: certificate signed by unknown authority
Retrying “registry.balena.ihost.net.ua/v2/c6fc9e5173e5db367cb5766323c575e9:latest” after 2.80s (2 of 3) due to: Error: Get https://re gistry.balena.ihost.net.ua/v2/: x509: certificate signed by unknown authority
Retrying “registry.balena.ihost.net.ua/v2/c6fc9e5173e5db367cb5766323c575e9:latest” after 3.92s (3 of 3) due to: Error: Get https://re gistry.balena.ihost.net.ua/v2/: x509: certificate signed by unknown authority
[Debug] Saving image registry.balena.ihost.net.ua/v2/c6fc9e5173e5db367cb5766323c575e9
[Debug] Untagging images…
[Info] Saving release…
[Error] Deploy failed
Error: Get https://registry.balena.ihost.net.ua/v2/: x509: certificate signed by unknown authority
at Stream. (/snapshot/balena-cli/node_modules/docker-progress/index.js:53:19)
at Stream.emit (events.js:189:13)
at Stream.EventEmitter.emit (domain.js:441:20)
at drain (/snapshot/balena-cli/node_modules/through/index.js:36:16)
at Stream.stream.queue.stream.push (/snapshot/balena-cli/node_modules/through/index.js:45:5)
at Parser.exports.parse.parser.onToken (/snapshot/balena-cli/node_modules/JSONStream/index.js:132:18)
at Parser.proto.write (/snapshot/balena-cli/node_modules/jsonparse/jsonparse.js:135:34)
at Stream. (/snapshot/balena-cli/node_modules/JSONStream/index.js:23:12)
at Stream.stream.write (/snapshot/balena-cli/node_modules/through/index.js:26:11)
at IncomingMessage.ondata (_stream_readable.js:689:20)
at IncomingMessage.emit (events.js:189:13)
at IncomingMessage.EventEmitter.emit (domain.js:441:20)
at addChunk (_stream_readable.js:284:12)
at readableAddChunk (_stream_readable.js:265:11)
at IncomingMessage.Readable.push (_stream_readable.js:220:10)
at HTTPParser.parserOnBody (_http_common.js:122:22)
at Socket.socketOnData (_http_client.js:442:20)
at Socket.emit (events.js:189:13)
at Socket.EventEmitter.emit (domain.js:441:20)
at addChunk (_stream_readable.js:284:12)
at readableAddChunk (_stream_readable.js:265:11)
at Socket.Readable.push (_stream_readable.js:220:10)
at Pipe.onStreamRead (internal/stream_base_commons.js:94:17)

If you need help, don’t hesitate in contacting our support forums at
https://forums.balena.io

For bug reports or feature requests, have a look at the GitHub issues or
create a new one at: https://github.com/balena-io/balena-cli/issues/

I did all in manual:
I have env NODE_EXTRA_CA_CERTS=/home/sergg/open-balena/config/certs/root/ca.crt
and i did:
sudo cp ca.crt /usr/local/share/ca-certificates/ca.crt sudo update-ca-certificates

Please help me .

Hey @sergbbb did you try restarting docker after setting the NODE_EXTRA_CA_CERTS env var? If I remember correctly that should be a required step

Thanks! It is works now! Please add this to manual:

Because, there is no information about docker restart after installing ca.crt.

Thanks again! =)

Great to know :slight_smile:
Yes absolutely, I already asked the openBalena team to add it there. Thanks for bringing this up