valgring

[Renato Filho]

Hi Guys,

My app is crashing on startup when running on "strict" mode, I tried
to add more verbose debug but until now I did not find the problem.

I would like to run the app with valgrind. This will make the
developer apps easy. Is that possible?

I already tried to install valgrind with my app adding it into the
"stage-packages" list. And use the snap shell to run the app and
valgrind. But did not work, it says:

"valgrind: failed to start tool 'memcheck' for platform 'amd64-linux':
No such file or directory"

Looking for this error on the internet it says that this is caused
because you are trying to run valgrind in a different path from the
"--prefix" used on the compilation time.

Have any of you guys already used valgrind to debug your snapped apps?
Do you have anithing to share?

Thanks
Renato

-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

xterm

[Joe Coates]

The main app in my snapped feature wants to initiate some xterm sessions and 
run a different local snap command in each.  However, I can't manage to get a 
terminal emulator of any sort to behave correctly within the snap (if they 
startup at all, then they cannot receive keystroke input).  I have tried xterm, 
rxvt, and the vte-based sakura as staged-packages.   Plugging to the X11 slot 
interface (and even Unity7) seems to have no effect.They build OK but fail 
at runtime with similar failures :

>/snap/exfab/x1/usr/bin/sakura: error while loading shared libraries: 
>libgtk-3.so.0: cannot open shared object file: No such file or directory
>/snap/exfab/x1/usr/bin/rxvt-xterm: error while loading shared libraries: 
>libX11.so.6: cannot open shared object file: No such file or directory
>/snap/exfab/x1/usr/bin/xterm: error while loading shared libraries: 
>libXft.so.2: cannot open shared object file: No such file or directory

My target machine is a Xenial VM in VirtualBox . . .
Does anyone do terminal emulation from a snap ?

Thanks,
Joe



DISCLAIMER:
This e-mail and any attachments to it may contain confidential and proprietary 
material and is solely for the use of the intended recipient. Any review, use, 
disclosure, distribution or copying of this transmittal is prohibited except by 
or on behalf of the intended recipient. If you have received this transmittal 
in error, please notify the sender and destroy this e-mail and any attachments 
and all copies, whether electronic or printed.
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Confined Docker snap available

[Loïc Minier]

Hi,

What's the output of snap --version?

Thanks!
- Loïc Minier

On Tue, Nov 1, 2016 at 4:21 AM, Peng Liu  wrote:

> Hi Loïc,
>
> I encountered some errors when I tried to connect the interfaces, for
> example:
> 
> sudo snap connect docker:docker-cli docker:docker-daemon
>
> error: cannot perform the following tasks: - Connect docker:docker-cli to
> docker:docker-daemon (cannot connect plug "docker-cli" from snap "docker",
> no such plug) 
>
> Then I am not able to run a simple docker command like "docker run --rm
> hello-world"
>
> Did I miss something? Is there anything need to do after installing the
> docker snap?
> Thanks.
>
> Peng
>
> On Tue, Oct 18, 2016 at 6:48 AM, Loïc Minier 
> wrote:
>
>> Hi!
>>
>> Docker is since some days available as a properly confined snap. This
>> will work on top of classic Ubuntu 16.04+ or on top of an up-to-date Ubuntu
>> Core series 16.
>>
>> Because the docker.sock path is hardcoded in a lot of images, this snap
>> conflicts with docker debs, so make sure you remove them first:
>> sudo apt purge docker docker-engine
>>
>> Create a system group for docker:
>> sudo groupadd --system docker
>>
>> Install the snap:
>> sudo snap install docker
>>
>> And connect the interfaces (these will go away we have a snap-declaration
>> in place):
>> sudo snap connect docker:docker-cli docker:docker-daemon
>> sudo snap connect docker:firewall-control ubuntu-core:firewall-control
>> sudo snap connect docker:support ubuntu-core:docker-support
>> sudo service snap.docker.dockerd stop
>> sudo service snap.docker.dockerd start
>>
>> You're now ready to use docker, e.g.:
>> sudo /snap/bin/docker run --rm -it hello-world
>> sudo /snap/bin/docker run --rm -it ubuntu
>>
>> At the moment, the Docker snap is available for amd64, armhf, arm64, i386.
>>
>> Docker-compose is also included, and may be used with the
>> "docker.compose" command.
>>
>> Want to read more about docker? Read the Docker snap status and FAQ doc
>> 
>> !
>>
>> Have fun and please report issues against https://github.com/doc
>> ker-snap/docker
>>
>> Cheers,
>> - Loïc Minier
>>
>> --
>> Snapcraft mailing list
>> Snapcraft@lists.snapcraft.io
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
>> an/listinfo/snapcraft
>>
>>
>


-- 
- Loïc
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Client authentication for private snap stores?

[Dan Kegel]

We might like to have snap stores which require a client to have a
certain certificate to be able to connect and download packages, just
as one can do with apt.

I think the way go works, the word 'Certificates' would be in the
source tree for snapd if this were already supported but I don't
see i there, which makes me think nobody's gotten around to supporting
the
idea of access-controlled snap stores.

Or did I miss something?

-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Client authentication for private snap stores?

[Mark Shuttleworth]

If you are using snaps as a format, you can build your own app store
easily enough.

In the Ubuntu store, IIRC we support several approaches you can take
advantage of:

 - snaps scoped to a specific device
 - snaps priced for purchase (like a phone app store)

... and combinations of those, where prices can be set for specific
devices by the brand.

Mark


On 01/11/16 21:29, Dan Kegel wrote:
> We might like to have snap stores which require a client to have a
> certain certificate to be able to connect and download packages, just
> as one can do with apt.
>
> I think the way go works, the word 'Certificates' would be in the
> source tree for snapd if this were already supported but I don't
> see i there, which makes me think nobody's gotten around to supporting
> the
> idea of access-controlled snap stores.
>
> Or did I miss something?
>



-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Client authentication for private snap stores?

[Marcos Alano]

A private app store supports authentication?

On 01/11/2016 17:56, Mark Shuttleworth wrote:
> If you are using snaps as a format, you can build your own app store
> easily enough.
>
> In the Ubuntu store, IIRC we support several approaches you can take
> advantage of:
>
>  - snaps scoped to a specific device
>  - snaps priced for purchase (like a phone app store)
>
> ... and combinations of those, where prices can be set for specific
> devices by the brand.
>
> Mark
>
>
> On 01/11/16 21:29, Dan Kegel wrote:
>> We might like to have snap stores which require a client to have a
>> certain certificate to be able to connect and download packages, just
>> as one can do with apt.
>>
>> I think the way go works, the word 'Certificates' would be in the
>> source tree for snapd if this were already supported but I don't
>> see i there, which makes me think nobody's gotten around to supporting
>> the
>> idea of access-controlled snap stores.
>>
>> Or did I miss something?
>>
>
>


-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Client authentication for private snap stores?

[Dan Kegel]

I have no problem with the server side; I'm sure I can add client cert
support to the
https://github.com/noise/snapstore demo.

The question is the 'snap install' command.
How do you install a client certificate for it to
use while contacting an app store that uses https client certificate
authentication?
- Dan

On Tue, Nov 1, 2016 at 12:59 PM, Marcos Alano  wrote:
> A private app store supports authentication?
>
> On 01/11/2016 17:56, Mark Shuttleworth wrote:
>> If you are using snaps as a format, you can build your own app store
>> easily enough.
>>
>> In the Ubuntu store, IIRC we support several approaches you can take
>> advantage of:
>>
>>  - snaps scoped to a specific device
>>  - snaps priced for purchase (like a phone app store)
>>
>> ... and combinations of those, where prices can be set for specific
>> devices by the brand.
>>
>> Mark
>>
>>
>> On 01/11/16 21:29, Dan Kegel wrote:
>>> We might like to have snap stores which require a client to have a
>>> certain certificate to be able to connect and download packages, just
>>> as one can do with apt.
>>>
>>> I think the way go works, the word 'Certificates' would be in the
>>> source tree for snapd if this were already supported but I don't
>>> see i there, which makes me think nobody's gotten around to supporting
>>> the
>>> idea of access-controlled snap stores.
>>>
>>> Or did I miss something?
>>>
>>
>>
>
>
> --
> Snapcraft mailing list
> Snapcraft@lists.snapcraft.io
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/snapcraft

-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: snap integration with XFCE

[PC Actual]

Hi Didier, hi all.

I've been trying to accomplish this mission but I miss something (my bet is
that I need an interface similar to gsettings but it doesn't exist
something like this).

1.- I have successfully created a symlink from
/home/$USER/.config/xfce4/xfconf/xfce-perchannel-xml inside the snap
directory and all the XML files in which the configuration is stored are
accessible for the application.

2.- I have defined, as stage package, xfconf, the tool to write
configurations directly into those XML files.

3.- But when I execute ' xfconf-query --channel xfce4-desktop --property
/backdrop/screen0/monitor0/workspace0/last-image --set wallpaper.jpg'
inside my application, I still receive 'Property
"/backdrop/screen0/monitor0/workspace0/last-image" does not exist on
channel "xfce4-desktop". If a new property should be created, use the
--create option.' and xfce-destop.xml (the XML which has the configuration
for the background wallpaper) is not modified at all.

Maybe is needed an interface similar to gsettings? If this is the case, can
I program something like that?

Thank you very much! :)

Best,

Eloy

2016-10-24 11:08 GMT+02:00 Didier Roche :

> Le 24/10/2016 à 10:58, Eloy García (PC Actual) a écrit :
> > Hi Didier!
> >
> > Thanks as always for your answer and feedback :) I suspected it and I
> > was taking a look to desktop launcher source code on github, but I
> > didn't have time to test it. One question: Can I create the symblink
> > when the snap application is executed (after installation) via the
> > script that i use to wrap up the launching process or will I have
> > problems to do that because of the confinement?
>
> No worry :)
>
> As long as your snap has the right plug to access the initial file, this
> isn't an issue (and exactly what I'm doing in the desktop launcher for
> dconf/gsettings: creating symlink on first launch or after each snap
> upgrade if the symlink isn't present).
> You can see such an example in
> https://github.com/ubuntu/snapcraft-desktop-helpers/blob/master/glib-only/
> launcher-specific#L37
> for instance.
>
> (But yeah, it relies on /home/$USER/ and should probably find a better
> way to get user's real home directory. I can't use $HOME as it's
> redirected to SNAP_USER_DATA in some cases)
>
>
> >
> > Best,
> >
> > Eloy
> >
> > 2016-10-24 10:14 GMT+02:00 Didier Roche  > >:
> >
> > Le 06/10/2016 à 21:34, Eloy García (PC Actual) a écrit :
> >> Hi all.
> >>
> >> I develop a java-based application to download and manage
> >> wallpapers from the Internet (wallpaperdownloader)
> >> (https://bitbucket.org/eloy_garcia_pca/wallpaperdownloader/overview
> ).
> >> The applications is in the store but now I'm trying to integrate
> >> XFCE desktop too. I mean, now you can set any wallpaper downloaded
> >> directly from the GUI and it is working fine for GNOME 3, Unity
> >> and MATE. All three of them use gsettings interface and
> >> desktop-gtk3 wrapper part as you can see in the snapcraft.yaml:
> >>
> >> name: wallpaperdownloader
> >> version: "2.2"
> >> summary: Download and manage your favorite wallpapers from the
> Internet
> >> description: WallpaperDownloader is a simple GUI Java based
> application for
> >> downloading and managing wallpapers from the Internet
> >> grade: stable
> >> confinement: strict
> >>
> >> apps:
> >>   wallpaperdownloader:
> >> command: wallpaperdownloader.sh
> >> plugs: [x11, network-bind, home, gsettings]
> >>
> >> parts:
> >>   # Pulls the code from the original source (master branch)
> >>   # desktop/gtk3 is a snapcraft part (snapcraft-desktop-helpers)
> >> from the Wiki: https://wiki.ubuntu.com/snapcraft/parts
> >> 
> >>   # It enables desktop integration and gsettings manipulation from
> >> the confined application
> >>   # It is necessary to use gsettings interface (see above) in order
> >> to have a fully functional
> >>   # desktop/gtk3 part
> >>   # Github repository for snapcraft-desktop-helpers:
> >> https://github.com/ubuntu/snapcraft-desktop-helpers
> >> 
> >>   wallpaperdownloader:
> >> plugin: maven
> >> source: ..
> >> stage-packages:
> >>   # mate-desktop-common is necessary to have MATE gsettings
> schemas
> >> available for the application
> >>   - mate-desktop-common
> >> after: [desktop/gtk3]
> >>
> >>   # It will copy wallpaperdownloader script into /bin/
> >>   # This script contains all the commands needed (sets env
> >> variables, launches the jar file...) to
> >>   # execute the application
> >>   exec:
> >> plugin: dump
> >> source: scripts
> >> Now, if XFCE desktop is detected by the application

Re: Provisional snap for DUB (D language package/build manager)

[Joseph Rushton Wakeling]

On 27/10/16 22:13, Joseph Rushton Wakeling wrote:

On 27/10/16 08:37, Didier Roche wrote:

I would look at /var/log/syslogs. Apparmor and seccomp denials are
listed there. Note that if you didn't already, you should really start
developping your snap in devmode. That way, it will get confinment out
of the equasion to get your relocatable code and dependencies working.
Then, we can turn on confinement and figure out those issues to be able
to publish in the stable channel.


Yea, I probably should have started with devmode.  Thanks for the advice about
syslogs; I'll check it out and see what I can find.


OK, so it looks like apparmor was indeed responsible.  The loglines in question:

Oct 30 17:50:50 computername kernel: [ 9532.992875] audit: type=1400 
audit(1477846250.853:43): apparmor="DENIED" operation="link" 
profile="snap.dub.dub" 
name="/home/username/code/D/dgraph/build/dgraph_graphtest" pid=22464 comm="dub" 
requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 
target="/home/username/code/D/dgraph/.dub/build/application-debug-linux.posix-x86_64-ldc_0-B7AFC7F4AA486AA98C5445F91F5653DB/dgraph_graphtest"
Oct 30 17:50:50 computername kernel: [ 9533.035303] audit: type=1326 
audit(1477846250.897:44): auid=4294967295 uid=1000 gid=1000 ses=4294967295 
pid=22464 comm="dub" exe="/snap/dub/x1/bin/dub" sig=31 arch=c03e syscall=92 
compat=0 ip=0x7f9b72d13717 code=0x0


I'm not experienced with apparmor, so could someone explain exactly what this 
means?  (I get the general idea, but the specifics would be useful to understand 
precisely.)


In particular, is there an obvious reason why this might be showing up with the 
dub snap, when the earlier ldc2 snap didn't have this problem?  I would guess 
because the ldc2 instance used by the snap-packaged dub is internal to the snap 
and does not benefit from the home-directory interface that dub itself gets?


Setting the containment to devmode removes the problem, but it would be nice to 
be able to have strict confinement earlier rather than later.


--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Provisional snap for DUB (D language package/build manager)

[Sergio Schvezov]

El 01/11/16 a las 23:31, Joseph Rushton Wakeling escribió:

On 27/10/16 22:13, Joseph Rushton Wakeling wrote:

On 27/10/16 08:37, Didier Roche wrote:

I would look at /var/log/syslogs. Apparmor and seccomp denials are
listed there. Note that if you didn't already, you should really start
developping your snap in devmode. That way, it will get confinment out
of the equasion to get your relocatable code and dependencies working.
Then, we can turn on confinement and figure out those issues to be able
to publish in the stable channel.


Yea, I probably should have started with devmode.  Thanks for the 
advice about

syslogs; I'll check it out and see what I can find.


OK, so it looks like apparmor was indeed responsible.  The loglines in 
question:


Oct 30 17:50:50 computername kernel: [ 9532.992875] audit: type=1400 
audit(1477846250.853:43): apparmor="DENIED" operation="link" 
profile="snap.dub.dub" 
name="/home/username/code/D/dgraph/build/dgraph_graphtest" pid=22464 
comm="dub" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 
target="/home/username/code/D/dgraph/.dub/build/application-debug-linux.posix-x86_64-ldc_0-B7AFC7F4AA486AA98C5445F91F5653DB/dgraph_graphtest"
Oct 30 17:50:50 computername kernel: [ 9533.035303] audit: type=1326 
audit(1477846250.897:44): auid=4294967295 uid=1000 gid=1000 
ses=4294967295 pid=22464 comm="dub" exe="/snap/dub/x1/bin/dub" sig=31 
arch=c03e syscall=92 compat=0 ip=0x7f9b72d13717 code=0x0


I'm not experienced with apparmor, so could someone explain exactly 
what this means?  (I get the general idea, but the specifics would be 
useful to understand precisely.)


If this is x86_64, everything is aligned with the world, syscall 92 is 
chown. A useful tool here can help you out, and luckily there is one, 
run `snap install snappy-debug` and it will do some nice things to 
figure out what is going on wth these apparmor and seccomp blockers.




In particular, is there an obvious reason why this might be showing up 
with the dub snap, when the earlier ldc2 snap didn't have this 
problem?  I would guess because the ldc2 instance used by the 
snap-packaged dub is internal to the snap and does not benefit from 
the home-directory interface that dub itself gets?

It seems to be just a dub problem.



Setting the containment to devmode removes the problem, but it would 
be nice to be able to have strict confinement earlier rather than later.


If this is the problem and you can patch the software then removing the 
chown could work, I am CCing Jamie for other ideas that could come up.


--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Confined Docker snap available

[Peng Liu]

Hi Loïc,

I also realized that might be a problem in an old version. So I upgraded
the snapd to the latest version.

$ snap --version
snap 2.16ubuntu3
snapd 2.16ubuntu3
series 16
ubuntu 16.04

And I tried to install the docker from both stable and edge channel.
In both cases, the plug and slot can not connect problems have gone. But I
am still not able to figure out how to run a simple hello world docker.

$ docker run ubuntu /bin/echo 'Hello world'
docker: Cannot connect to the Docker daemon. Is the docker daemon running
on this host?.
See 'docker run --help'.

Thanks.

Peng

On Tue, Nov 1, 2016 at 11:06 AM, Loïc Minier  wrote:

> Hi,
>
> What's the output of snap --version?
>
> Thanks!
> - Loïc Minier
>
> On Tue, Nov 1, 2016 at 4:21 AM, Peng Liu  wrote:
>
>> Hi Loïc,
>>
>> I encountered some errors when I tried to connect the interfaces, for
>> example:
>> 
>> sudo snap connect docker:docker-cli docker:docker-daemon
>>
>> error: cannot perform the following tasks: - Connect docker:docker-cli to
>> docker:docker-daemon (cannot connect plug "docker-cli" from snap "docker",
>> no such plug) 
>>
>> Then I am not able to run a simple docker command like "docker run --rm
>> hello-world"
>>
>> Did I miss something? Is there anything need to do after installing the
>> docker snap?
>> Thanks.
>>
>> Peng
>>
>> On Tue, Oct 18, 2016 at 6:48 AM, Loïc Minier 
>> wrote:
>>
>>> Hi!
>>>
>>> Docker is since some days available as a properly confined snap. This
>>> will work on top of classic Ubuntu 16.04+ or on top of an up-to-date Ubuntu
>>> Core series 16.
>>>
>>> Because the docker.sock path is hardcoded in a lot of images, this snap
>>> conflicts with docker debs, so make sure you remove them first:
>>> sudo apt purge docker docker-engine
>>>
>>> Create a system group for docker:
>>> sudo groupadd --system docker
>>>
>>> Install the snap:
>>> sudo snap install docker
>>>
>>> And connect the interfaces (these will go away we have a
>>> snap-declaration in place):
>>> sudo snap connect docker:docker-cli docker:docker-daemon
>>> sudo snap connect docker:firewall-control ubuntu-core:firewall-control
>>> sudo snap connect docker:support ubuntu-core:docker-support
>>> sudo service snap.docker.dockerd stop
>>> sudo service snap.docker.dockerd start
>>>
>>> You're now ready to use docker, e.g.:
>>> sudo /snap/bin/docker run --rm -it hello-world
>>> sudo /snap/bin/docker run --rm -it ubuntu
>>>
>>> At the moment, the Docker snap is available for amd64, armhf, arm64,
>>> i386.
>>>
>>> Docker-compose is also included, and may be used with the
>>> "docker.compose" command.
>>>
>>> Want to read more about docker? Read the Docker snap status and FAQ doc
>>> 
>>> !
>>>
>>> Have fun and please report issues against https://github.com/doc
>>> ker-snap/docker
>>>
>>> Cheers,
>>> - Loïc Minier
>>>
>>> --
>>> Snapcraft mailing list
>>> Snapcraft@lists.snapcraft.io
>>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
>>> an/listinfo/snapcraft
>>>
>>>
>>
>
>
> --
> - Loïc
>
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Confined Docker snap available

[Peng Liu]

Oh, I figured out the root cause. It's the permission.

After added the user to the docker group, I can run docker commands now.
$sudo gpasswd -a ${USER} docker

Docker snap works perfectly! Thanks.


On Tue, Nov 1, 2016 at 6:26 PM, Peng Liu  wrote:

> Hi Loïc,
>
> I also realized that might be a problem in an old version. So I upgraded
> the snapd to the latest version.
>
> $ snap --version
> snap 2.16ubuntu3
> snapd 2.16ubuntu3
> series 16
> ubuntu 16.04
>
> And I tried to install the docker from both stable and edge channel.
> In both cases, the plug and slot can not connect problems have gone. But I
> am still not able to figure out how to run a simple hello world docker.
>
> $ docker run ubuntu /bin/echo 'Hello world'
> docker: Cannot connect to the Docker daemon. Is the docker daemon running
> on this host?.
> See 'docker run --help'.
>
> Thanks.
>
> Peng
>
> On Tue, Nov 1, 2016 at 11:06 AM, Loïc Minier 
> wrote:
>
>> Hi,
>>
>> What's the output of snap --version?
>>
>> Thanks!
>> - Loïc Minier
>>
>> On Tue, Nov 1, 2016 at 4:21 AM, Peng Liu  wrote:
>>
>>> Hi Loïc,
>>>
>>> I encountered some errors when I tried to connect the interfaces, for
>>> example:
>>> 
>>> sudo snap connect docker:docker-cli docker:docker-daemon
>>>
>>> error: cannot perform the following tasks: - Connect docker:docker-cli
>>> to docker:docker-daemon (cannot connect plug "docker-cli" from snap
>>> "docker", no such plug) ==
>>> ==
>>>
>>> Then I am not able to run a simple docker command like "docker run --rm
>>> hello-world"
>>>
>>> Did I miss something? Is there anything need to do after installing the
>>> docker snap?
>>> Thanks.
>>>
>>> Peng
>>>
>>> On Tue, Oct 18, 2016 at 6:48 AM, Loïc Minier 
>>> wrote:
>>>
 Hi!

 Docker is since some days available as a properly confined snap. This
 will work on top of classic Ubuntu 16.04+ or on top of an up-to-date Ubuntu
 Core series 16.

 Because the docker.sock path is hardcoded in a lot of images, this snap
 conflicts with docker debs, so make sure you remove them first:
 sudo apt purge docker docker-engine

 Create a system group for docker:
 sudo groupadd --system docker

 Install the snap:
 sudo snap install docker

 And connect the interfaces (these will go away we have a
 snap-declaration in place):
 sudo snap connect docker:docker-cli docker:docker-daemon
 sudo snap connect docker:firewall-control ubuntu-core:firewall-control
 sudo snap connect docker:support ubuntu-core:docker-support
 sudo service snap.docker.dockerd stop
 sudo service snap.docker.dockerd start

 You're now ready to use docker, e.g.:
 sudo /snap/bin/docker run --rm -it hello-world
 sudo /snap/bin/docker run --rm -it ubuntu

 At the moment, the Docker snap is available for amd64, armhf, arm64,
 i386.

 Docker-compose is also included, and may be used with the
 "docker.compose" command.

 Want to read more about docker? Read the Docker snap status and FAQ doc
 
 !

 Have fun and please report issues against https://github.com/doc
 ker-snap/docker

 Cheers,
 - Loïc Minier

 --
 Snapcraft mailing list
 Snapcraft@lists.snapcraft.io
 Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
 an/listinfo/snapcraft


>>>
>>
>>
>> --
>> - Loïc
>>
>
>
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft