I am cross-posting this here since it may be a Snap issue and not a Node one.
https://github.com/nodesource/distributions/issues/663
This issue appears to prevent the VSCode snap from working correctly for me (wrt extensions). Related downstream issues:
1 Like
It looks like here the classic snap code
is trying to execute a classic snap node
and failing, correct?
If so, then this seems to be a duplicate of Snapd 2.32 breaks live-server installer. I seem to recall @jdstrand saying he had an idea on how to solve this kind of issue some clever way (hopefully not too clever
). Am I remembering correctly?
In the example, classic snap node
cannot execute snap hello
. In my real world example, classic snap code
(powered by Node) cannot execute classic snap go
.
Is there a Snapcraft issue filed on GitHub or Launchpad that I can follow?
Yeah, I think you are right @ijohnson
@Jayschwa if I understood right back in the day, it would be more an Apparmor issue, but @jdstrand knows for sure.
I commented in the upstream node bug that this is https://bugs.launchpad.net/snapd/+bug/1835805. I also updated https://bugs.launchpad.net/bugs/1849753 and added a comment to 1835805 for it.
2 Likes