<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/4.8.5"> </HEAD> <BODY> On Thu, 2015-10-08 at 12:48 -0700, Vani Desai wrote: <BLOCKQUOTE TYPE=CITE> Thanks Ted. Your suggestions worked. I see cherrypy webserver running at launch. I can access cherrypy hello world webpage on my host PC browser. </BLOCKQUOTE> Great! <BLOCKQUOTE TYPE=CITE> 1. I see this message "Signature check failed, but installing anyway as requested" when I install a snap on Snappy QEMU. How do I get valid signature for my snap? </BLOCKQUOTE> The signature comes from the store, if you want you can upload your snap to the store and then any device running snappy can install it with a "snappy install" command. There is a lot more information on the store itself: <A HREF="https://myapps.developer.ubuntu.com/dev/click-apps/?format=snap">https://myapps.developer.ubuntu.com/dev/click-apps/?format=snap</A> <BLOCKQUOTE TYPE=CITE> 2. I installed snappy example py3-project on Snappy QEMU. It has sha3sum.py. I can't run that python program on Snappy. How to execute program installed with Snap manually? </BLOCKQUOTE> If you look at the snapcraft file for that example: <A HREF="http://bazaar.launchpad.net/~snappy-dev/snapcraft/core/view/head:/examples/py3-project/snapcraft.yaml">http://bazaar.launchpad.net/~snappy-dev/snapcraft/core/view/head:/examples/py3-project/snapcraft.yaml</A> You can see the name of the package is "spongeshaker" and the name of the binary is "sha3sum". So there will be a binary in the path called: <TT>spongeshaker.sha3sum</TT> You can execute it using that. If you'd like to see the script that is generated that is in <TT>/apps/bin/</TT> <BLOCKQUOTE TYPE=CITE> 3. I have webdm installed on Snappy QEMU.I am not able to access webdm from my host PC browser. I tried webdm.local:8080 or localhost:8080 </BLOCKQUOTE> What command did you use to start QEMU? The command on the webpage maps that port into the local QEMU session's 4200. But if you don't do a mapping QEMU won't pull out the ports into localhost. I'm not sure, but I don't believe the mDNS support will work in QEMU (the .local address) without a more complex network config. Ted </BODY> </HTML>