These are chat archives for resin-io/chat

9th
Mar 2016
Craig Mulligan
@craig-mulligan
Mar 09 2016 08:17
Maybe a cool demo for the new beast? - http://arcweb.github.io/chappiecast/
@curcuz you may also be interested ^
Craig Mulligan
@craig-mulligan
Mar 09 2016 12:57
I guess it comes down to playing html5 vid on rpi :/
Shaun Mulligan
@shaunmulligan
Mar 09 2016 13:08
as always :/
Niels Bertram
@bertramn
Mar 09 2016 13:10
Hi @jviotti, I did actually remove the cache image and downloaded it again for the raspi2 however I got the same outcome. I grabbed the ole pi 1 and did the same for that one and was able to create a working SD card for the old model.
Carlo Maria Curinga
@curcuz
Mar 09 2016 13:38
@craig-mulligan @shaunmulligan
(Gitter mobile apparently auto sends a message if you click on a link while typing) @craig-mulligan @shaunmulligan it could be achieved piping it to omxplayer instead of the DOM
Shaun Mulligan
@shaunmulligan
Mar 09 2016 13:45
sweet, that would be awesome to see. I think we would also need to use something like raspi2fb to copy the framebuffer of HDMI over to the smaller piTFT screens
Carlo Maria Curinga
@curcuz
Mar 09 2016 13:48
@shaunmulligan can't you just tell omxplayer to use that screen?
Juan Cruz Viotti
@jviotti
Mar 09 2016 13:49
@bertramn That’s weird. Let me try myself on the rpi2.
Juan Cruz Viotti
@jviotti
Mar 09 2016 14:46

@bertramn It works fine for me. This is the exact size of the raspberry-pi2.img here:

$ stat -f "%z” $HOME/.resin/cache/raspberry-pi2.img
1577058304

Can you confirm this is the size you have?

Andrei Gherzan
@agherzan
Mar 09 2016 17:37
Good news! Raspberrypi 3 support is not available on https://dashboard.resin.io . Enjoy.
Shaun Mulligan
@shaunmulligan
Mar 09 2016 18:04
@agherzan I think you mean not -> NOW!!
Dominik Kukacka
@dominikkukacka
Mar 09 2016 18:07
perfect! i got my rpi3 just some hours ago :smile:
Dominik Kukacka
@dominikkukacka
Mar 09 2016 18:27

@agherzan @shaunmulligan it seems the nodejs container is not available for raspberry3

Error while processing push: Error: Error: image resin/raspberrypi3-node:4.0.0 not found

Shaun Mulligan
@shaunmulligan
Mar 09 2016 18:29
@dominikkukacka yeah, since the RPI3 doesnt make use of the 64bit arch, we will just be using the raspberrypi2 images
Carlo Maria Curinga
@curcuz
Mar 09 2016 18:30
@shaunmulligan @telphan is the rpi3 mainstream already?
I mean can we drop the alpha image?
Shaun Mulligan
@shaunmulligan
Mar 09 2016 18:30
but its a good point, we should have an alias for the raspberrypi3- images to their raspberrypi2- counter parts
@curcuz yup it just went to production now
burn the alpha image with :fire:
Dominik Kukacka
@dominikkukacka
Mar 09 2016 18:31
so should i try using the rpi2-image?
Carlo Maria Curinga
@curcuz
Mar 09 2016 18:31
@shaunmulligan hahaha i will but it served good for testing ;)
Andrei Gherzan
@agherzan
Mar 09 2016 18:31
@shaunmulligan good catch. :)
Dominik Kukacka
@dominikkukacka
Mar 09 2016 18:31
ah just read it :)
just a thing about using the rpi2 container for rpi3: we can't use %%RESIN_ARCH%% then
Shaun Mulligan
@shaunmulligan
Mar 09 2016 18:34
yup, that is where having the alias will help :smiley:
Dominik Kukacka
@dominikkukacka
Mar 09 2016 18:34
yep :smiley:
otherwise GOOD JOB!
Dominik Kukacka
@dominikkukacka
Mar 09 2016 19:50
mhm
09.03.16 20:49:49 [+0100] Downloading application 'registry.resin.io/timterminal/accef174bb0b1f145003164fdb0722a7d8d0e4c0'
09.03.16 20:50:00 [+0100] Failed to download application 'registry.resin.io/timterminal/accef174bb0b1f145003164fdb0722a7d8d0e4c0' due to 'Error pulling image (latest) from registry.resin.io/timterminal/accef174bb0b1f145003164fdb0722a7d8d0e4c0, HTTP code 400'
i restartet the rpi3, let's see if this helps
nope
still
09.03.16 20:53:12 [+0100] Downloading application 'registry.resin.io/timterminal/accef174bb0b1f145003164fdb0722a7d8d0e4c0'
09.03.16 20:53:25 [+0100] Failed to download application 'registry.resin.io/timterminal/accef174bb0b1f145003164fdb0722a7d8d0e4c0' due to 'Error pulling image (latest) from registry.resin.io/timterminal/accef174bb0b1f145003164fdb0722a7d8d0e4c0, HTTP code 400'
Craig Mulligan
@craig-mulligan
Mar 09 2016 20:00
Hey @dominikkukacka repushing the application should solve the problem.
Docker registry v1 sometimes has issues with uploading images when you have an s3 backend, it reports everything was successful, only when you try to pull and there isn’t anything there it returns a 400 error. We are migrating to Docker registry v2 but its a process so we still occassionally see this v1 bug.
Dominik Kukacka
@dominikkukacka
Mar 09 2016 20:02
i am trying it right now :)
ah ok, yeah i heard about the docker reg v1 problem
Dominik Kukacka
@dominikkukacka
Mar 09 2016 20:08
ywwww yissss :)
boots
Craig Mulligan
@craig-mulligan
Mar 09 2016 20:09
Nice!
Think you maybe the first after @curcuz! reply to our tweet with a pic and we'll send you some shwagg!
Dominik Kukacka
@dominikkukacka
Mar 09 2016 21:45
just did! whatever shwagg is :D
Dominik Kukacka
@dominikkukacka
Mar 09 2016 22:09
hey, another question: can i somehow suppress the "Booted - Check your resin.io dashboard"? And where is this located? I can't find anything in the repos :)
Theodor Gherzan
@telphan
Mar 09 2016 22:20
@dominikkukacka yes, you can. The service that brings that ascii art is this: https://github.com/resin-os/meta-resin/blob/master/meta-resin-common/recipes-support/resin-info/resin-info-tty/tty-replacement.service. So all you have to do is disable that service, which is easy, just delete this file located on your image's rootfs /etc/systemd/system/multi-user.target.wants/tty-replacement.service. This is just a temporary fix until we get to implement this as user configurable.