Re: From ROS prototype to production on Ubuntu Core (part 1)
Kyle, A big thank you for driving this and getting snaps and Ubuntu Core more visibility. This is very timely and serves to answer a lot of difficult questions people have been asking on the mailers on ROS and content sharing. Keep up the great work! Cheers, Manik On Thu, Apr 6, 2017 at 3:59 PM, Kyle Fazzariwrote: > Hey everyone, > > This is really for those on the list who are using ROS (Robot Operating > System), but it may prove beneficial to others as well. > > I've been working on creating a blog/video series about taking a ROS > prototype to production using snaps and Ubuntu Core. Barring any > unforeseen circumstances, I plan to publish one part per week. > > Part 1 has been published, if you're interested in checking it out. > > Blog post: > https://kyrofa.com/posts/from-ros-prototype-to-production- > on-ubuntu-core-1-5 > Video: https://youtu.be/x6BkzfwOZbc > > Thanks! > > -- > Kyle Fazzari (kyrofa) > Software Engineer > Canonical Ltd. > k...@canonical.com > > > -- > 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: Big snaps on ubuntu store.
On Thu, Apr 6, 2017 at 5:57 AM, Jose Pekkarinen < jose.pekkari...@canonical.com> wrote: > I'll do later today with the bug report. > > Yes it's possible to slim it, as this is bringing all clang targets with > all the bells and whistles the git code brings, however I see no way how to > put some targets in a slimmer snap without duplicating the common part in > all the others. I'm open to suggestions. > you can put the common part in 1 snap and share it via the content interface with all the other snaps. since you are the publisher of these snaps, the interfaces can also be auto-connected on installation. the only issue i see is that users will have to install at least 2 different snaps (if not more). /manik -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
Re:
this is really cool leo. thanks for sharing. i'll definitely give it a try. /manik On Tue, Mar 28, 2017 at 10:20 AM, Leo Ariaswrote: > Hello, > > It has never been easier, snapcraft and profit! > > For a couple of weeks we have been figuring out how to confine > bitcoin. This is one of the most important use cases of the snap > security because you don't want any program messing with your digital > wallet. And when there's a vulnerability in the code, all the clients > should be updated as fast as possible to keep the network sane. With > snaps, just push a fixed version and see everybody update without any > work from their side. > > We now need help testing the snap before making it public: > > $ sudo snap install bitcoin --candidate > > Then launch it from the dash or running the bitcoin.qt command. > > This was built from the tag of the latest released bitcoin and pushed > to the store, all automatically by travis. But, be warned, you will be > the first users so we might still find unforeseen problems. Use your > bitcoins with caution during the candidate phase, or just test without > any of your money. > > Here are the sources for the snap and CI scripts, in case you want to > verify them or build it yourself: > https://github.com/elopio/blockchain-snaps/blob/master/ > bitcoin/snap/snapcraft.yaml > > Another interesting detail is that most of the cryptocurrencies out > there are forks of the bitcoin source code, so they will all need a > similar snapcraft.yaml. The other one we pushed is bitcoin-unlimited, > which is promoting a hard fork of the bitcoin network to remove the > block size limit. You can have both snaps installed to give them a try > and choose the network you want to support, because both will be fully > confined and independent: > > $ sudo snap install bitcoin-unlimited --candidate > > Of course, this would require twice the time and space to download > both blockchains. > > Thanks to Gal Buki (torusJKL) for his help. > > Expect more options in the store soon. > > pura vida > -- > ¡paz y baile! > http://www.ubuntu.com > > -- > 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: build.snapcraft.io and GitHub groups
On Fri, Mar 17, 2017 at 4:49 PM, Joseph Rushton Wakeling < joseph.wakel...@webdrake.net> wrote: > Hello all, > > I thought I'd give build.snapcraft.io a go for my ldc2 snap. Signing in > was fine, and I was asked to give permission both for accessing my account > and the ldc-developers group which I'm part of (where the ldc2 snap is > managed). > > However, when being asked to choose a GitHub repo, I was presented only > with repos from my own personal GitHub, and none belonging to > ldc-developers -- so I couldn't add the official repo of the ldc2 snap. > > This was a little bit surprising given that I was explicitly asked to OK > access by build.snapcraft.io to the ldc-developers group, so ... any > chance this could be addressed? :-) > > Assuming it might not be soon, I assume the best option would be to use > Launchpad as documented here: > https://snapcraft.io/docs/build-snaps/ci-integration > > ... but is it possible to do this via a project registered on behalf of a > team, instead of an individual user account? > Yes, OpenHAB project is doing exactly that- https://code.launchpad.net/~openhab/openhab-snap/+git/master Cheers, Manik -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
Re: RAID on NextCloud
much appreciated simon! On Tue, Mar 14, 2017 at 11:13 PM, Simon Fels <simon.f...@canonical.com> wrote: > On 15.03.2017 00:39, Manik Taneja wrote: > > hi there, > > > > an interesting question came up on askubuntu- > > > > https://askubuntu.com/questions/888404/ubuntu-core-with-raid-1?rq=1 > > > > is the best solution to package mdadm as a snap with core providing > > an interface to /dev/md*? are there alternate solutions? > > We had a pretty active discussion a while back when we implemented the > udisks2 interface in snapd. The outcome was that we don't want to give > arbitrary snaps access to block devices and added all access for those > directly into the udisks2 interface (see [0]). > > udisks2 offers a mediated way for all other snaps to deal with block > devices and generally also allows working with RAIDs. I say generally, > because this is a feature we didn't verified yet that it is working with > the udisks2 snap currently in the store. > > If support for RAIDs in udisks2 works users should be able to mount a > RAID on a directory in /media via an dbus API call. > > One downside is that the udisks2 interface explicitly denies plug > connections as it still gives kind of privileged access to the system. > Every mount done via udisks2 will appear below /media and every snap > using the removable-media interface will get access to devices mounted > there, regardless if it's the system partition or not. So even the plug > side is a very privileged thing. That said, snaps can ask for a > snap-declaration on the store side to get connections to udisks2. > > Another feature we support with the udisks2 snap is auto-mounting. This > allows a device to say that it wants removable devices like USB storage > device to be automatically mounted in /media as you know it from > consumer oriented devices like the Ubuntu Desktop. Depending on how the > RAID is setup this might be able to get the the RAID mounted on boot > into /media. Requirements for the automounter to consider a device are > currently: > > * Device is not a system device (meaning its not a partition on the > device we're booting the system from) > * Device is not already mounted > * Device is a removable devices (USB, CD/DVD) > > For a very simple, unconfined solution you could just install the > udisks2 snap (given that it detects and works well with RAID devices) > and create a systemd unit in /etc/systemd/system/mount-my-raid.service > > [Unit] > Description=Mount my RAID > > [Service] > Exec=/snap/bin/udisks2.udisksctl mount -b /path/to/block/device > > [Install] > WantedBy=multi-user.target > > Then activate it via > > $ sudo systemctl enable mount-my-raid.service > > and the RAID should be automatically mounted below /media on the next > system reboot. > > I hope this helps. > > Btw. I will post this as an answer to the askubuntu.com question too. > > regards, > Simon > > > [0]: > https://github.com/snapcore/snapd/blob/master/interfaces/ > builtin/udisks2.go > > -- > 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
RAID on NextCloud
hi there, an interesting question came up on askubuntu- https://askubuntu.com/questions/888404/ubuntu-core-with-raid-1?rq=1 is the best solution to package mdadm as a snap with core providing an interface to /dev/md*? are there alternate solutions? /manik -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
Re: New stable "core" and "ubuntu-core" snaps released
On Tue, Feb 21, 2017 at 9:25 AM, Paul Larsonwrote: > > 5. disable updates (for added paranoia, because yes I really did see a > stable update to a snap that triggered a reboot in the middle of a > test once!) > how are you disabling updates? fyi, the systemd.update-timer is no more.. /manik -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
Re: New stable "core" and "ubuntu-core" snaps released
On Thu, Feb 16, 2017 at 12:15 PM, Max Brustkernwrote: > > > On Thu, Feb 16, 2017 at 9:55 AM, Michael Vogt > wrote: > >> Hello, >> >> The Snappy team is happy to announce the promotion of snapd 2.22.2 >> from the candidate channel to stable in both the "core" and >> "ubuntu-core" snaps. It will also be available via the regular apt >> update mechanism in Ubuntu 14.04, 16.04 and 16.10. Other distributions >> will follow on their own schedule. >> >> > I'd like to trigger tests to run when new core snaps are available in the > stable and candidate channels. What's the best way to check that? > i suspect that you will like to run tests after installing a newer rev of a snap from the candidate/stable channels. at the moment, i believe your best option is to poll the store for a newer revision. once available, update the device explicitly using snap refresh and than run whatever tests you like. if its a snap that you published yourself, you could run hooks on install automatically that can trigger whatever tests you like. moving forward, we will need to work on a better approach via push-notifications (perhaps) that will tell a device about a new revision and also allow the capability to install it immediately, instead of waiting for the next update-timer to kick in. /manik -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
Re: LDC compiler snap issues on 14.04 (ABI compatibility?)
jamie, any insights? /manik On Wed, Feb 15, 2017 at 3:09 PM, Joseph Rushton Wakeling < joseph.wakel...@webdrake.net> wrote: > On 11/02/17 17:31, Joseph Rushton Wakeling wrote: > >> I just reproduced the issue in a VirtualBox install of 14.04 to get these >> details. Kernel report in kern.log: >> >> Feb 11 17:16:19 vb1404 kernel: [ 534.781526] traps: gcc[6209] general >> protection ip:7f6632d1b1ee sp:7fff0a09e2f0 error:0 in >> libc-2.23.so[7f6632bd8000+1bf000] >> >> And `dmesg | grep -i gcc` gave this output: >> >> [0.00] Linux version 4.4.0-62-generic (buildd@lcy01-33) (gcc >> version >> 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #83~14.04.1-Ubuntu SMP Wed Jan 18 >> 18:10:30 UTC 2017 (Ubuntu 4.4.0-62.83~14.04.1-generic 4.4.40) >> [ 534.781526] traps: gcc[6209] general protection ip:7f6632d1b1ee >> sp:7fff0a09e2f0 error:0 in libc-2.23.so[7f6632bd8000+1bf000] >> >> This may give enough information for someone to suggest the next step. >>> >> >> I'm not very experienced at interpreting these kinds of messages, but if I >> understand right they would suggest a libc compatibility issue ... ? >> > > Folks, could I ping on the above? > > It seems like a rather severe limitation on the universality of the > package (at a minimum it probably restricts the package to working on > systems with the same or later libc) so I'm curious if anyone has any > thoughts on if and how this could be ameliorated. > > > -- > Snapcraft mailing list > Snapcraft@lists.snapcraft.io > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm > an/listinfo/snapcraft > -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
Re: Is there any way to list all of the configure options for a snap application?
> On Feb 7, 2017, at 10:14 PM, XiaoGuo Liuwrote: > > Hi, > > According to the article at > https://github.com/snapcore/snapd/blob/master/tests/lib/snaps/snapctl-hooks/meta/hooks/configure, > we can configure a snap using "snap get/set" command. Is there any way to > list all of the configuration options for a snap app so that an end user can > fine-tune the app. No, this is in the roadmap but not implemented yet! > > Thanks & best regards, > XiaoGuo > > -- > XiaoGuo, Liu > -- > 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
snapcraft parts cache and webservice
hi there, just wanted to find out the status of- https://trello.com/c/R4PP2b8P/142-parts-build-cache-and-webservice cheers, manik -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
Re: Pi2 and 3 image improvements (GLES, GPIO)
Fantastic work Ogra. Cheers, Manik On Wed, Jan 18, 2017 at 10:59 AM, Oliver Grawertwrote: > hi, > > at [1] you can now find a daily image build for the Pi2 and Pi3 that > both have full GLES support and all 26 GPIOs exposed through > interfaces, some test feedback would be nice :) > > the GPIO numbering and pin mapping follows the community map at [2] and > looks like [3] in the "snap interfaces" output now. > > ciao > oli > > [1] http://people.canonical.com/~ogra/snappy/all-snaps/daily/current/ > [2] http://pinout.xyz/# > [3] http://paste.ubuntu.com/23822613/ > -- > 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: Locally extending trusted certificates
hi there, just wanted to follow-up on this query and see if we have a solution to this problem? /manik On Fri, Jan 6, 2017 at 9:17 AM, Loïc Minierwrote: > Hi, > > This question came up in the context of Docker registries with self-signed > certificates: > http://askubuntu.com/questions/868268/add-self-signed-certif > icate-in-ubuntu-core-16-04 > this could be addressed in ways specific to the Docker snap, but I believe > this touches a larger question: support for extending the list of > system-trusted certificates. > > Our Ubuntu Core images ship with a set of trusted certificates. These are > inherited from the .deb world where there is a mechanism to locally extend > the list of trusted certificates (update-ca-certificates). This mechanism > doesn't work with core images due to read-only directories (and perhaps > other issues as well). > > Here are some possible options to address this: > 1) fix the update-ca-certificates system to also work on core images; this > might just be a matter of making some directories bind-mounts to the > writable space > > 2) implement some kind of snapd keystore feature/configs/APIs (much like > system keystores on mobile OSes); this is likely significant work, but > opens interesting perspectives in providing new management APIs and a more > secure implementation. For instance, one could design this to store secrets > in hw-specific secure stores, or offer mechanisms to roll out new > certificates/keys via assertions, or to disable some specific CAs > > 3) keep the list of system certificates as static and not locally > configurable; this will likely result in some snaps developing alternate > keystores > > I'm sure there are other options and I'd to hear how people think this > should best be addressed in the snap/snapd world. > > Cheers, > - Loïc Minier > > -- > 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: create-user primitive
On Wed, Jan 18, 2017 at 4:33 AM, Gustavo Niemeyerwrote: > Don't see a reason to go beyond not listing it. The command works fine, > including proper help and reasonable error messages. > > The reason it prevents creating users when one already exists is so we > don't see scripts opening back doors by mistake. As Michael points out, > this may be overriden with --force-managed. > > i would suggest that we document this somewhere. the only way i knew about its existence was the fact that i had seen the primitive in an earlier version of snapd. for others who are not familiar, this might not even show up on their radar. /manik -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
Re: Hi
Sunny, Can you please mail your request in to <snapcraft@lists.snapcraft.io>. /Manik On Tue, Jan 17, 2017 at 10:54 PM, Sunny Bhayani < sunny.bhay...@einfochips.com> wrote: > Hi Manik, > > > Thank you for your time. > > > Actually, we have some technical query, related to the ubuntu-image binary > which builds the ubuntu-os. > > > So is this the right forum ? > > If not, then I request you to please connect me to the right person. > > > I have already posted my query on the Rocketchat #snapcraft and #snappy > channels for the same, but the query is open. > > > Keeping in loop my manager Mr. Ajay Pandey. > > > Thanks & Regards, > *Sunny Bhayani* > Solution Consultant | Solutions > Tel: - | Cell: 919909705699 > Product Engineering Services > Software | System | Silicon | Mechanical > > www.einfochips.com | sunny.bhay...@einfochips.com > <https://einfochips.com/blog/> > <https://www.linkedin.com/company/einfochips> > <https://www.facebook.com/eInfochips> > <https://plus.google.com/115387550354383133244/posts> > <https://twitter.com/einfochipsltd> > <https://www.youtube.com/user/einfochipsindia?feature=watch> > <http://www.slideshare.net/eInfochips_Solution> > 20 Years of Engineering Innovation & Excellence > Recognized as 'Leader' in Zinnov's Global Service Providers Rating-2015 > > -- > *From:* Manik Taneja <ma...@canonical.com> > *Sent:* Wednesday, January 18, 2017 7:12:50 AM > *To:* Sunny Bhayani > *Cc:* Prakash Advani > *Subject:* Hi > > Hi Sunny, > > Hope this email finds you well. Thanks for reaching out on linkedin. I was > wondering as to where are you based and if you were connected to Prakash, > our Dir of Sales India. In any case, please let us know how we can help. > > Regards, > Manik > > > * eInfochips Business Disclaimer: > This e-mail message and all attachments transmitted with it are intended > solely for the use of the addressee and may contain legally privileged and > confidential information. If the reader of this message is not the intended > recipient, or an employee or agent responsible for delivering this message > to the intended recipient, you are hereby notified that any dissemination, > distribution, copying, or other use of this message or its attachments is > strictly prohibited. If you have received this message in error, please > notify the sender immediately by replying to this message and please delete > it from your computer. Any views expressed in this message are those of the > individual sender unless otherwise stated. Company has taken enough > precautions to prevent the spread of viruses. However the company accepts > no liability for any damage caused by any virus transmitted by this email. > > > * > -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
Re: create-user primitive
On Tue, Jan 17, 2017 at 4:01 PM, Michael Hudson-Doyle < michael.hud...@canonical.com> wrote: > On 18 January 2017 at 12:13, Manik Taneja <ma...@canonical.com> wrote: > >> >> >> On Tue, Jan 17, 2017 at 1:30 PM, Michael Hudson-Doyle < >> michael.hud...@canonical.com> wrote: >>> >>> >>> Well snap create-user is mostly there exactly so that console-conf can >>> invoke it. That's also why it's hidden from snap help! >>> >> thanks for the insights michael. in addition, is there a way to- >> >>- remove the user created via create-user? >> >> I don't know. > >> >>- add local users? >> >> Yes, you can you adduser with the --extrausers flag. > thanks michael! -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
Re: New stable "core" and "ubuntu-core" snaps released
On Thu, Jan 5, 2017 at 9:25 AM, Leo Ariaswrote: > Could you please explain what is ubuntu-core and core? > *ubuntu-core* has been renamed to just *core*. > In an old machine I have ubuntu-core, and I can't get core installed in > there. > i had a similar issue and the only way i could get this corrected was to explicity uninstall and reinstall snapd. /manik -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
Re: store errors
On Wed, Jan 4, 2017 at 6:02 AM, Bret A. Barkerwrote: > That's hitting the service to fetch assertions, nothing to do with the CDN. > > What version of snapd are you on? 2.20 includes more robust network error > handling and retries. > Thanks Bret. I was on 2.18 and just refreshed to 2.20. Will keep an eye out for this one. /Manik -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
Re: Cannot install snap apps from store
> On Dec 8, 2016, at 11:13 PM, Michael Nelson <michael.nel...@canonical.com> > wrote: > >> On Fri, Dec 9, 2016 at 5:39 PM Manik Taneja <manik.tan...@canonical.com> >> wrote: >>> On Dec 8, 2016, at 8:21 PM, Oliver Ries <oliver.r...@canonical.com> wrote: >>> Hi >>> >>> On Thu, Dec 8, 2016 at 6:31 PM, XiaoGuo Liu <xiaoguo@canonical.com> >>> wrote: >>> Hi, >>> >>> I do not know how many of you have met the issue. When I try to install an >>> app from the store, it comes me an error like: >>> >>> liuxg@ubuntu:~$ sudo snap install tensorflow-demo --devmode --beta >>> error: cannot install "tensorflow-demo": Get >>> https://search.apps.ubuntu.com/api/v1/snaps/details/tensorflow-demo?channel=beta: >>> net/http: request canceled while waiting for connection (Client.Timeout >>> exceeded while awaiting headers) >>> liuxg@ubuntu:~$ sudo snap install tensorflow-demo --devmode --beta >>> error: cannot install "tensorflow-demo": Get >>> https://search.apps.ubuntu.com/api/v1/snaps/details/tensorflow-demo?channel=beta: >>> net/http: request canceled while waiting for connection (Client.Timeout >>> exceeded while awaiting headers) >> >> This has been usually because of CDN issues afaik. The store team should >> able to confirm shortly. > > In this case, it's an issue just with the initial connection from the client > to search.apps.ubuntu.com, before following any CDN url to download the snap. > I also tried to reproduce around 40mins after XiaoGuo and couldn't. > > After trying to reproduce, I checked the apache logs for > search.apps.ubuntu.com and saw that during that time it only ever saw > requests which resulted in 200 replies: > > http://paste.ubuntu.com/23602216/ > > There were no relevant errors in the error log that I could see, nor does our > monitoring show any high load at the time, so unless apache isn't logging > timeouts, I suspect the requests weren't getting through to > search.apps.ubuntu.com for some network-related reason, but I'm keen for > someone else on the store team to check the networking and logs. > > We have seen this before intermittently, so please if you see a client > timeout as above, add your data to: > > https://bugs.launchpad.net/click-package-index/+bug/1639981 > > and we'll keep digging. Just to add, I have seen this issue intermittently a few times before. Next time, I'll capture logs and add to the bug. Please list out all that you need captured.. > > Thanks! > -Michael > >> >> Can you check status.snapcraft.io to see any outages around the date you >> experienced this? >> >>> >>> I just did a quick test on my classic Ubuntu (AMD64) and was able to >>> download & install the snap just fine. >>> >>> In fact, I have met this this problem a number of times, and sometimes it >>> works fine. Also, my colleague said to me that he gets the same issue >>> sometimes. What is the root cause for this? >>> >>> it might be good to get this into a bug report with all relevant >>> information (distribution, architecture, network setup (traceroute?) and a >>> timestamp so server logs can be matched. >>> >>> let us know the id and the team will be looking at that asap. >>> >>> thx, >>> Olli >>> -- >>> 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 > -- > 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: Cannot install snap apps from store
> On Dec 8, 2016, at 8:21 PM, Oliver Rieswrote: > > Hi > >> On Thu, Dec 8, 2016 at 6:31 PM, XiaoGuo Liu >> wrote: >> Hi, >> >> I do not know how many of you have met the issue. When I try to install an >> app from the store, it comes me an error like: >> >> liuxg@ubuntu:~$ sudo snap install tensorflow-demo --devmode --beta >> error: cannot install "tensorflow-demo": Get >> https://search.apps.ubuntu.com/api/v1/snaps/details/tensorflow-demo?channel=beta: >> net/http: request canceled while waiting for connection (Client.Timeout >> exceeded while awaiting headers) >> liuxg@ubuntu:~$ sudo snap install tensorflow-demo --devmode --beta >> error: cannot install "tensorflow-demo": Get >> https://search.apps.ubuntu.com/api/v1/snaps/details/tensorflow-demo?channel=beta: >> net/http: request canceled while waiting for connection (Client.Timeout >> exceeded while awaiting headers) This has been usually because of CDN issues afaik. The store team should able to confirm shortly. Can you check status.snapcraft.io to see any outages around the date you experienced this? > > I just did a quick test on my classic Ubuntu (AMD64) and was able to download > & install the snap just fine. > >> In fact, I have met this this problem a number of times, and sometimes it >> works fine. Also, my colleague said to me that he gets the same issue >> sometimes. What is the root cause for this? > > it might be good to get this into a bug report with all relevant information > (distribution, architecture, network setup (traceroute?) and a timestamp so > server logs can be matched. > > let us know the id and the team will be looking at that asap. > > thx, > Olli > -- > 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: docker snap not working
On Tue, Dec 6, 2016 at 8:48 AM, Jamie Bennett <jamie.benn...@canonical.com> wrote: > Yes, thanks to mvo we will test Docker as part of the usual test battery. > Is LXD part of this process as well? If not, than please include it as well! > > Regards, > Jamie. > > On 6 Dec 2016, at 16:34, Loïc Minier <loic.min...@ubuntu.com> wrote: > > Michael Vogt just added this check; nice! > > https://github.com/snapcore/snapd/pull/2421 > > On Tue, Dec 6, 2016 at 3:34 PM, Mark Shuttleworth <m...@ubuntu.com> wrote: > >> >> Can we add Docker to a list of 'critical snaps' that is part of our >> pre-release validation suite? >> >> Mark >> >> >> On 06/12/16 05:05, Manik Taneja wrote: >> >> >> >> On Dec 6, 2016, at 4:51 AM, Loïc Minier <loic.min...@ubuntu.com> wrote: >> >> Hi, >> >> On Tue, Dec 6, 2016 at 3:49 AM, Peng Liu <pengliu.m...@gmail.com> wrote: >> >>> There is some known issue of the docker snap, check the google doc for >>> detailed information. >>> https://docs.google.com/document/d/1JHa6tkuR9PtpnAVVmAJIAKuy >>> KBy8E9ZkvG5Wbc6HZSY/edit# >>> >>> And you need to make sure your snapd is the latest version. >>> >> >> Exactly; it only affects Ubuntu Core images (not snaps on classic), and >> there are two workarounds: >> - either install the snap with devmode >> - or run this after boot (and then restart dockerd): >> >> $ sudo nsenter -m/run/snapd/ns/docker.mnt >> >> # umount --lazy /var/lib/snapd/hostfs/sys >> The fix is in snap-confine git and is planned for upload this Friday. >> >> Thanks Loic! >> >> >> Best regards, >> - Loïc Minier >> >> -- >> Snapcraft mailing list >> Snapcraft@lists.snapcraft.io >> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm >> an/listinfo/snapcraft >> >> >> >> >> >> -- >> 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 > > > > -- > 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: configure hook
+kyle On Sun, Nov 6, 2016 at 11:51 PM, Didier Rochewrote: > Le 06/11/2016 à 00:22, Boris Rybalkin a écrit : > > > > Hello, > > > > Hey Boris, > > > > I want to generate my config on snap install using snap location > > variables. > > > > From the docs configure hook is only triggered when 'snap set' is > > called. Will configure also be called on install and upgrade? > > > I didn't try it myself yet, but from what I heard yeah, they will be run > at that time. Kyle can confirm (and if so, we'll update to the > documentation to reflect that). > > Cheers, > Didier > > -- > 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: Removing a key
On Thu, Oct 13, 2016 at 1:48 PM, Luke Williamswrote: Hello, > > I was trying to build an Ubuntu-Core image and noticed that I don't have > my original snap key on my newly rebuilt system (hard drive failure on my > build machine) so I created a new default key, but can't upload it since I > already have a key named default. I ended up creating a new key with a new > name, but I would like to remove the original key, but can't seem to find > anything on how to do this. I can see the keys with snapcraft list-keys but > no way to remove them. Any ideas? > > try this- snapcraft revoke-key /manik -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
Re: Announce: LXD available as a snap
Thank you Stephane and the LXD team. This is fantastic news for machine container aficionados. Its time to start testing this out :) /Manik On Tue, Oct 11, 2016 at 4:20 PM, Stéphane Graberwrote: > Hello, > > As of a few minutes ago, LXD is now available as a snap in the stable > channel. > This has been confirmed to work on both Ubuntu 16.04 and 16.10, provided > that snapd and snap-confine are perfectly up to date. > > If you want to try it, pick a machine that you're NOT using LXD on and do: > - apt remove --purge lxd lxd-client > - groupadd --system lxd > - snap install lxd > - lxd init > - lxd.lxc launch ubuntu:16.04 xenial > > This will remove your existing LXD to prevent any confusion between the > snap and packaged version, will ensure that you have a "lxd" group on > your system and then install LXD. Note that the daemon can take a little > while to startup on first installation, so you may have to retry the > "lxd init" step. > > And that's it, you've got LXD running with your first container! > > The default values in lxd init will get you a ZFS backed storage and a > working network for your containers. > > Our channel setup looks something like: > - stable (manual, latest release) > - candidate (semi-automatic, staging area for stable) > - beta (manual, unused currently) > - edge (automatic, auto-upload when git master changes) > > Note that edge can be updated up to 5-6 times a day (as it was today). > > Known limitations (sorted by priority): > - "lxd" group must exist ahead of time: https://bugs.launchpad.net/ > snappy/+bug/1606510 > - Updating the snap restarts all containers: https://bugs.launchpad.net/ > snappy/+bug/1632508 > - Can't provide the "lxc" command: https://bugs.launchpad.net/ > snappy/+bug/1607748 > - LXD always runs even when unused: https://bugs.launchpad.net/ > snappy/+bug/1612440 > - No powerpc build due to lack of snapcraft support: > https://bugs.launchpad.net/snapcraft/+bug/1632091 > - Unable to build using a specific commit: https://bugs.launchpad.net/ > snapcraft/+bug/1632126 > - Ability to distribute multiple upstream series: > https://bugs.launchpad.net/snappy/+bug/1611424 > > The LXD team will be working with the Snappy team to address the above > limitations. > With those sorted, we'll be able to make the LXD snap the best way to > experience LXD. > > > If you run into issues, please file bugs! > - For LXD bugs: https://github.com/lxc/lxd/issues > - For packaging bugs: https://github.com/lxc/lxd-pkg-ubuntu/issues > - If unsure, file against LXD. > > Enjoy! > > Stéphane > > -- > 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 sources
On Mon, Oct 10, 2016 at 5:41 PM, Chris <cpoll...@embarqmail.com> wrote: > On Mon, 2016-10-10 at 16:06 -0700, Manik Taneja wrote: > > > > > > > > On Mon, Oct 10, 2016 at 2:45 PM, Chris <cpoll...@embarqmail.com> > > wrote: > > > Other than those shown here - https://uappexplorer.com/apps?type=sn > > > appy > > > =title are there other places to get Snaps from? > > uappexplorer is just a web frontend to the Ubuntu Store > > infrastructure, which is our > > repository of snaps. There are no other publicly available snap repos > > that we are > > aware of. Are you just looking to find out the exhaustive list of > > snaps available for > > consumption? or you are trying to solve something else? > > > > Cheers, > > Manik > > > Thanks Manik, I was looking for the available snaps. I'm using a few so > far and I really like the way they work and the ease of installation. > > That's great. Welcome to the club! /Manik -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
Re: Different values of environment variables during build time and run time, eg. JAVA_HOME and PATH
On Mon, Oct 10, 2016 at 6:33 AM, Jian LUOwrote: > Hi List, > > Is there any formal way in snapcraft to set environment variables > separately for build time and run time? The use case I'm facing is building > a Java snap on amd64 host for armhf target. > Snapcraft does not support cross-compilation. Consider building natively on armhf, or using this as reference- https://github.com/snapcore/snapd/blob/master/docs/cross-build.md and let us know if you see any issues. /Manik -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
Re: ntopng strict snap published
On Tue, Aug 9, 2016 at 11:39 AM, Evan Dandreawrote: > On Mon, 8 Aug 2016 at 17:51 Sergio Schvezov > wrote: > >> El 08/08/16 a las 13:35, Blake Rouse escribió: >> > I would like to setup some travis CI that will auto upload tip of >> > dev into the edge channel of "ntopng". >> >> Evan has some guides for setting up CI and could also solve or point you >> in the right direction to take the reserved name. >> >> snapcraft 2.15 should be able to allow setting up macaroons through env >> vars (to make it easier to use things like travis-ci) but that shouldn't >> stop you from using ev's current solution. >> > > This will let you build and publish snaps off Travis runs. You'll want to > change $MACAROON_SECRET to your favourite value from pwgen. You'll also > need to change the snap name and the $TRAVIS_BRANCH conditional. > > https://gist.github.com/evandandrea/998180be091518da1f6330bf19ed7a40 > > will this allow them to claim the reserved name? -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft