Debugging `confinement: strict` issues

[Zygmunt Krynicki]

You should see useful hints in the system log (use journalctl to see
it). Most of the errors boil down to one of two cases: forbidden
system call (the message will just contain the system call number
along with some techno babble) and forbidden filesystem path (the
message will indicate the path, the word DENIED and the operation that
was requested but got denied).

If you find those you know where to start. Please share your findings.

Mounted network shares won't be visible AFAIR. Home will be
auto-connected as of the next version but for now you need to connect
it manually with "snap connect yoursnapname:home ubuntu-core:home".

Best regards.
ZK

On Tue, Jun 7, 2016 at 4:56 PM, Reinhard Pointner
<reinhard.pointner at gmail.com> wrote:
> Hi all,
>
> Does anyone have any hints on how to debug issues that only happen in
> non-devmode? Like logging when certain "interfaces" are used?
>
> I'm working on snapping a Java application, and I've got `plugs: [home,
> network]` in my snapcraft.yaml but the app can't write any files in the user
> home (home plug should give the app write access right? also, what about
> network shares mounted by the user?). Also, when making http requests that
> thread will just deadlock (no exceptions or and timeouts not respected, so i
> suspect lower level network api issues).
>
> Cheers,
> Reinhard
>
>
> --
> Snapcraft mailing list
> Snapcraft at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/snapcraft
>