getaddrinfo ENOTFOUND registry.yarnpkg.com registry.yarnpkg.com:443

[Alvaro Uria]

I've tried to build a snap in build.snapcraft.io but it looks it failed due to filtering reasons.

https://pastebin.canonical.com/208521/

Would it be possible to allow connections to registry.yarnpkg.com:443?

This is the snap that fails: https://github.com/auria/snap-grafana/

[Adam Collard (adam-collard)]

Hmm, I suspect this is caused by the manual invocation of yarn.

Snapcraft's node plugin has support for yarn installs which does the right dance to pass in the config for the proxy.

Is there a reason you're using ~/.npm-global ?

[Alvaro Uria (aluria)]

I am not so familiar with snaps so put all the building steps as described in Grafana's README.

I've now used node-package but still get the same error:
https://github.com/auria/snap-grafana/blob/master/snapcraft.yaml#L38

error An unexpected error occurred: "https://registry.yarnpkg.com/tinycolor2: getaddrinfo ENOTFOUND registry.yarnpkg.com registry.yarnpkg.com:443".
/build/ae01291f418f790aeb84a167f91878ca-xenial/parts/grafana-ui/npm/bin/yarn add grunt

If I don't add "grunt", it fails.

[Evan (ev)]

I confirmed with Adam out of band that this is likely an issue in the buildds:

https://build.snapcraft.io/user/evandandrea/yarn-snap-test/136744
https://github.com/evandandrea/yarn-snap-test

I think this should be a high priority, given lighthouse apps using yarn (https://build.snapcraft.io/user/heroku/cli).