EDIT (2020-06-10): Request changed from ‘classic’ confinement to autoconnecting interfaces. Disregard the initial request, now seeking approval for autoconnects. Original post is below:
Hello! I wrote a CLI static site generator in C# called Pigmeat, and, due to the issues Snapcraft has with .NET Core programs, I am forced to use ‘classic’ confinement.
The first technical issue I encountered was with the ‘dotnet’ plugin, which only supported up to .NET Core 2.2. I mitigated this issue using a custom plugin, with the code available on my respository: dotnet3.py.
However, the one issue which I cannot solve otherwise is the following error when attempting to run Pigmeat under ‘strict’ confinement:
Failed to create CoreCLR, HRESULT: 0x80070008
Besides the fact that this is a static site generator, which would already want traditional filesystem access to do its job, this needs to be under ‘classic’ confinement to run on a technical level. This appears to be related to snap’s issues with handling .NET Core 3.1 in general—something about the way the program is confined is making it impossible for the .NET runtime to work.
Thank you for taking the time to read. I would appreciate any and all further suggestions, though I would suggest cloning the git repository yourselves to see if the issue is merely on my side (though I do believe my testing was thorough).
EDIT: Wanted to mention that, while the technical issue remains, I do understand one should be using the ‘home’ and ‘removable-devices’ interfaces for a static site generator. Unfortunately, ‘classic’ confinement is still required to run the program, so this does not appear to be useful at the time being.