[00:22] <dhaker> help
[04:20] <mup> Bug #1591142 changed: snapd leaks files in /tmp <Snappy:Expired> <https://launchpad.net/bugs/1591142>
[04:20] <mup> Bug #1604356 changed: symlink creation over and over on install, creates file too long situation <Snappy:Expired> <https://launchpad.net/bugs/1604356>
=== JanC is now known as Guest95619
=== JanC_ is now known as JanC
[08:31] <lifeless> whats the right place to report bugs on images? specifically the generic amd64 image doesn't boot under hyper0v
[14:34] <mup> PR snapd#2358 closed: tests: decrease the number of expected featured apps <Created by fgimenez> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/2358>
[15:44] <eekfonky> I have just taken the plunge to install snappy on my Pi3. How do I make Docker start at boot and where can I edit the fstab to mount my external HD?
=== devil is now known as Guest23953
=== Guest23953 is now known as devil_
=== devil_ is now known as devil__
[15:49] <Chipaca> lifeless: i think that's lp:snappy still
[15:49] <Chipaca> eekfonky: docker should start on boot automatically
[15:50] <Chipaca> eekfonky: i'm not sure about mounting. Probably easiest is to drop a .mount unit in /etc/systemd/system
[15:51] <Chipaca> eekfonky: if this were a device you were building, i think it's the kind of thing that goes in the gadget.yaml
[15:56] <eekfonky> Cool, So Docker is sorted (although I have to use sudo and cannot do a usermod -aG) As for mounting I think it goes in the /writable section, but I don't want to tamper with it in case I break it
[15:59] <eekfonky> Do I need to add another fstab in /writable? or make a soft link? Is there a procedure for this? I am not sure how to write a .mount for the /etc/systemd/system. I know how to add a service like NZBget but mounting a drive...any advice?
=== devil__ is now known as devil_
=== vila is now known as wasnt-me
=== wasnt-me is now known as vila
=== devil is now known as Guest16179
=== Guest16179 is now known as devil_
=== JanC_ is now known as JanC