These are chat archives for resin-io/chat

29th
Feb 2016
Dominik Kukacka
@dominikkukacka
Feb 29 2016 10:06
yes i just ordered one :smile: let's see when it will be here in austria
how many do you have actually? is there a list?
Shaun Mulligan
@shaunmulligan
Feb 29 2016 11:32
@dominikkukacka did you get the electron app working? I might be that you need to increase the GPU memory split on the pi. by default it is set to 16mb, probably best to bump it up to something like 256mb
Also I dont think electron currently works on the RPI1, so that could also be an issue
Dominik Kukacka
@dominikkukacka
Feb 29 2016 11:33
i set RESIN_HOST_CONFIG_gpu_mem to 256
this should be enough right?
Shaun Mulligan
@shaunmulligan
Feb 29 2016 11:33
yeah, that should be all good
Dominik Kukacka
@dominikkukacka
Feb 29 2016 11:34
is it 256
or 256mb
mhm i am not sure which RPI i have now...
Shaun Mulligan
@shaunmulligan
Feb 29 2016 11:34
it should just be 256, dont need the mb
Dominik Kukacka
@dominikkukacka
Feb 29 2016 11:35
yes i did that
Shaun Mulligan
@shaunmulligan
Feb 29 2016 11:35
in the logs i see it says armv7l, so i guess it is the rpi2, so it should work
Dominik Kukacka
@dominikkukacka
Feb 29 2016 11:36
ok so thats not the problem
Shaun Mulligan
@shaunmulligan
Feb 29 2016 11:36
could you try push my test electron app, i was using it on an RPI2 last week: https://github.com/shaunmulligan/resin-electron-app
Dominik Kukacka
@dominikkukacka
Feb 29 2016 11:37
which is fine
ok i will try!
Shaun Mulligan
@shaunmulligan
Feb 29 2016 11:38
its also worth checking on the board if it is a RPI 2 or an RPI1, it should be printed above the CPU
Dominik Kukacka
@dominikkukacka
Feb 29 2016 11:39
ah ok, i am currently at work, i will check when i get home
for now i am going to push the resin-electron-app
let's see
and thank you for your help!!!
Shaun Mulligan
@shaunmulligan
Feb 29 2016 11:40
cool...let me know how it goes :smile: ..Im actually in the process of building an electron based smartphone on my RPI2, hoping to blog the beginnings of it later this week
Dominik Kukacka
@dominikkukacka
Feb 29 2016 11:41
woha haha :sparkles:
Shaun Mulligan
@shaunmulligan
Feb 29 2016 11:51
yeah, its a bit insane and unnecessary, but I got this awesome 3G module (https://learn.adafruit.com/adafruit-fona-3g-cellular-gps-breakout/overview) and 4.3" touch screen (http://www.thing-printer.com/product/manga-screen/) so its a good excuse to learn some new stuff :smile:
Dominik Kukacka
@dominikkukacka
Feb 29 2016 12:55
hehe nice stuff. i am currently looking at the 7" touchscreen for my project
but for now i want to get electron running just on my monitor
Shaun Mulligan
@shaunmulligan
Feb 29 2016 12:56
yeah i have one those guys too, they are really nice and touch works out the box :D
Dominik Kukacka
@dominikkukacka
Feb 29 2016 12:56
awesome :D
we are talking about the "original" one or?
so with the nice bezel around it
Shaun Mulligan
@shaunmulligan
Feb 29 2016 12:57
yeah, the official RPI LCD
Dominik Kukacka
@dominikkukacka
Feb 29 2016 12:57
nice
:smile:
Shaun Mulligan
@shaunmulligan
Feb 29 2016 12:59
yeah, I have been looking for a project to use it in, but havent had any major inspiration yet :P
Dominik Kukacka
@dominikkukacka
Feb 29 2016 13:18
hehe, yeah i have something in mind, just have to get it
ah just noticed
my rpi is a 256mb version
the max gpu_mem here is 192
probably this is then ignored?
Shaun Mulligan
@shaunmulligan
Feb 29 2016 13:19
hmm, so that can't be RPI2, i think the RPI2 has minimum 1GB ram
yeah it may be ignored, i would try set it to 192
or 128
but my suspicion is that electron still wont work :/
Dominik Kukacka
@dominikkukacka
Feb 29 2016 13:21
damn
yeah i am confused, there are so many versions of RPI
1/2/A/B/B+
haha
so i just ordered the RPI 3
Shaun Mulligan
@shaunmulligan
Feb 29 2016 13:22
yeah, their naming scheme is a bit confusing
sweet, we also have some on the way :D
that one will run electron no problem :smile:
Dominik Kukacka
@dominikkukacka
Feb 29 2016 13:23
so they are really already available? not only backorder?
i didn't hear back from pihut
how hard will the port of resin be?
Shaun Mulligan
@shaunmulligan
Feb 29 2016 13:33
yeah, from what I understand they are ready to ship, but I dont know the specifics. I dont think it will be too difficult for resin to support, @agherzan can probably give a better estimate of the work involved
Alexandros Marinos
@alexandrosm
Feb 29 2016 14:01
I have a hope that it might work out of the box, at least badly
but we won't know till we see them, as it is a new chip
Shaun Mulligan
@shaunmulligan
Feb 29 2016 14:02
well the wifi and BLE wont work out the box, since they are still working on the software
apparently the BLE part is not working yet
Dominik Kukacka
@dominikkukacka
Feb 29 2016 14:18
yep BLE is in the works
until we get the device in our hands, they probably have the new software ready :smile:
Shaun Mulligan
@shaunmulligan
Feb 29 2016 14:24
yeah, lets hope so :D
dlarm
@dlarm
Feb 29 2016 20:05
So I'm a bit confused on my custom image, should I have docker installed or rce?
I currently have rce, but it doesn't seem to want to run the images it knows about.
Alexandros Marinos
@alexandrosm
Feb 29 2016 20:24
rce is what you should have for now
but you shouldn't need to interact with it at all
@dlarm can you describe a bit more what you're trying to do or what symptoms you're seeing?
dlarm
@dlarm
Feb 29 2016 21:10
@alexandrosm Well I thought it was that I didn't have an application image uploaded, but it looks like rce can't start the resin_supervisor image
rce[14728]: Error response from daemon: No such container: resin_supervisor
Although it does see it as an image, but I cannot run it using rce commands directly
rce images
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
resin/armv7hf-supervisor latest 024f1f50898c 6 days ago 173.2 MB
resin/armv7hf-supervisor production 024f1f50898c 6 days ago 173.2 MB
Pablo Carranza Vélez
@pcarranzav
Feb 29 2016 21:11
hi @dlarm - the supervisor is run by resin-supervisor.service
could you post the output of systemctl status resin-supervisor?
dlarm
@dlarm
Feb 29 2016 21:12
it just says it failed with nothing else
Pablo Carranza Vélez
@pcarranzav
Feb 29 2016 21:12
hmm
and some more logs maybe, using journalctl?
maybe journalctl -fn 100
dlarm
@dlarm
Feb 29 2016 21:14
Feb 29 21:14:00 basestation systemd1: Starting Resin supervisor...
Feb 29 21:14:00 basestation rce[20936]: time="2016-02-29T21:14:00Z" level="info" msg="POST /v1.16/containers/resin_supervisor/stop?t=10"
Feb 29 21:14:00 basestation rce[20936]: time="2016-02-29T21:14:00Z" level="info" msg="+job stop(resin_supervisor)"
Feb 29 21:14:00 basestation rce[20936]: No such container: resin_supervisor
Feb 29 21:14:00 basestation rce[20936]: time="2016-02-29T21:14:00Z" level="info" msg="-job stop(resin_supervisor) = ERR (1)"
Feb 29 21:14:00 basestation rce[20936]: time="2016-02-29T21:14:00Z" level="error" msg="Handler for POST /containers/{name:.}/stop returned error: No such container: resin_supervisor"
Feb 29 21:14:00 basestation rce[20936]: time="2016-02-29T21:14:00Z" level="error" msg="HTTP Error: statusCode=404 No such container: resin_supervisor"
Feb 29 21:14:00 basestation rce[12583]: Error response from daemon: No such container: resin_supervisor
Feb 29 21:14:00 basestation rce[12583]: time="2016-02-29T21:14:00Z" level="fatal" msg="Error: failed to stop one or more containers"
Feb 29 21:14:00 basestation rce[20936]: time="2016-02-29T21:14:00Z" level="info" msg="DELETE /v1.16/containers/resin_supervisor?force=1"
Feb 29 21:14:00 basestation rce[20936]: time="2016-02-29T21:14:00Z" level="info" msg="+job rm(resin_supervisor)"
Feb 29 21:14:00 basestation rce[20936]: No such container: resin_supervisor
Feb 29 21:14:00 basestation rce[20936]: time="2016-02-29T21:14:00Z" level="info" msg="-job rm(resin_supervisor) = ERR (1)"
Feb 29 21:14:00 basestation rce[20936]: time="2016-02-29T21:14:00Z" level="error" msg="Handler for DELETE /containers/{name:.
} returned error: No such container: resin_supervisor"
Feb 29 21:14:00 basestation rce[20936]: time="2016-02-29T21:14:00Z" level="error" msg="HTTP Error: statusCode=404 No such container: resin_supervisor"
Feb 29 21:14:00 basestation systemd1: Started Resin supervisor.
Feb 29 21:14:00 basestation rce[12589]: Error response from daemon: No such container: resin_supervisor
Feb 29 21:14:00 basestation rce[12589]: time="2016-02-29T21:14:00Z" level="fatal" msg="Error: failed to remove one or more containers"
Feb 29 21:14:00 basestation systemd1: Starting Host socket for resin supervisor...
Feb 29 21:14:00 basestation systemd1: Started Host socket for resin supervisor.
Feb 29 21:14:01 basestation rce[20936]: time="2016-02-29T21:14:01Z" level="info" msg="POST /v1.16/containers/create?name=resin_supervisor"
Feb 29 21:14:01 basestation rce[20936]: time="2016-02-29T21:14:01Z" level="info" msg="+job create(resin_supervisor)"
Feb 29 21:14:02 basestation rce[20936]: time="2016-02-29T21:14:02Z" level="info" msg="+job log(create, 431093d71d60110a3dd250dcc5966abd625b5f5a7fc9e7766a53aeebb5a23e84, resin/armv7hf-supervisor:latest)"
Feb 29 21:14:02 basestation rce[20936]: time="2016-02-29T21:14:02Z" level="info" msg="-job log(create, 431093d71d60110a3dd250dcc5966abd625b5f5a7fc9e7766a53aeebb5a23e84, resin/armv7hf-supervisor:latest) = OK (0)"
Feb 29 21:14:02 basestation rce[20936]: time="2016-02-29T21:14:02Z" level="info" msg="-job create(resin_supervisor) = OK (0)"
Feb 29 21:14:02 basestation rce[20936]: time="2016-02-29T21:14:02Z" level="info" msg="POST /v1.16/containers/431093d71d60110a3dd250dcc5966abd625b5f5a7fc9e7766a53aeebb5a23e84/attach?stderr=1&stdout=1&stream=1"
Feb 29 21:14:02 basestation rce[20936]: time="2016-02-29T21:14:02Z" level="info" msg="+job container_inspect(431093d71d60110a3dd250dcc5966abd625b5f5a7fc9e7766a53aeebb5a23e84)"
Feb 29 21:14:02 basestation rce[20936]: time="2016-02-29T21:14:02Z" level="info" msg="-job container_inspect(431093d71d60110a3dd250dcc5966abd625b5f5a7fc9e7766a53aeebb5a23e84) = OK (0)"
Feb 29 21:14:02 basestation rce[20936]: time="2016-02-29T21:14:02Z" level="info" msg="+job attach(431093d71d60110a3dd250dcc5966abd625b5f5a7fc9e7766a53aeebb5a23e84)"
Feb 29 21:14:02 basestation rce[20936]: time="2016-02-29T21:14:02Z" level="info" msg="POST /v1.16/containers/431093d71d60110a3dd250dcc5966abd625b5f5a7fc9e7766a53aeebb5a23e84/start"
Feb 29 21:14:02 basestation rce[2093
Pablo Carranza Vélez
@pcarranzav
Feb 29 2016 21:15
that looks fine actually
the errors are because we try to stop/delete the old container if it's there
rce ps shows no output?
is there anything in /var/log/supervisor-log/?
dlarm
@dlarm
Feb 29 2016 21:16
looks like that cut off the entire log
Pablo Carranza Vélez
@pcarranzav
Feb 29 2016 21:16
cut off how?
dlarm
@dlarm
Feb 29 2016 21:17
Feb 29 21:14:02 basestation rce[20936]: time="2016-02-29T21:14:02Z" level="info" msg="+job start(431093d71d60110a3dd250dcc5966abd625b5f5a7fc9e7766a53aeebb5a23e84)"
Feb 29 21:14:02 basestation rce[20936]: time="2016-02-29T21:14:02Z" level="info" msg="+job log(start, 431093d71d60110a3dd250dcc5966abd625b5f5a7fc9e7766a53aeebb5a23e84, resin/armv7hf-supervisor:latest)"
Feb 29 21:14:02 basestation rce[20936]: time="2016-02-29T21:14:02Z" level="info" msg="-job log(start, 431093d71d60110a3dd250dcc5966abd625b5f5a7fc9e7766a53aeebb5a23e84, resin/armv7hf-supervisor:latest) = OK (0)"
Feb 29 21:14:02 basestation rce[20936]: time="2016-02-29T21:14:02Z" level="info" msg="+job release_interface(431093d71d60110a3dd250dcc5966abd625b5f5a7fc9e7766a53aeebb5a23e84)"
Feb 29 21:14:02 basestation rce[20936]: No network information to release for 431093d71d60110a3dd250dcc5966abd625b5f5a7fc9e7766a53aeebb5a23e84
Feb 29 21:14:02 basestation rce[20936]: time="2016-02-29T21:14:02Z" level="info" msg="-job release_interface(431093d71d60110a3dd250dcc5966abd625b5f5a7fc9e7766a53aeebb5a23e84) = ERR (1)"
Feb 29 21:14:02 basestation rce[20936]: time="2016-02-29T21:14:02Z" level="info" msg="+job release_interface(431093d71d60110a3dd250dcc5966abd625b5f5a7fc9e7766a53aeebb5a23e84)"
Feb 29 21:14:02 basestation rce[20936]: No network information to release for 431093d71d60110a3dd250dcc5966abd625b5f5a7fc9e7766a53aeebb5a23e84
Feb 29 21:14:02 basestation rce[20936]: time="2016-02-29T21:14:02Z" level="info" msg="-job release_interface(431093d71d60110a3dd250dcc5966abd625b5f5a7fc9e7766a53aeebb5a23e84) = ERR (1)"
Feb 29 21:14:02 basestation rce[20936]: time="2016-02-29T21:14:02Z" level="info" msg="+job log(die, 431093d71d60110a3dd250dcc5966abd625b5f5a7fc9e7766a53aeebb5a23e84, resin/armv7hf-supervisor:latest)"
Feb 29 21:14:02 basestation rce[20936]: time="2016-02-29T21:14:02Z" level="info" msg="-job log(die, 431093d71d60110a3dd250dcc5966abd625b5f5a7fc9e7766a53aeebb5a23e84, resin/armv7hf-supervisor:latest) = OK (0)"
Feb 29 21:14:02 basestation rce[20936]: Cannot start container 431093d71d60110a3dd250dcc5966abd625b5f5a7fc9e7766a53aeebb5a23e84: fork/exec /var/lib/rce/init/dockerinit-1.4.1: invalid argument
Feb 29 21:14:02 basestation rce[20936]: time="2016-02-29T21:14:02Z" level="info" msg="-job start(431093d71d60110a3dd250dcc5966abd625b5f5a7fc9e7766a53aeebb5a23e84) = ERR (1)"
Feb 29 21:14:02 basestation rce[20936]: time="2016-02-29T21:14:02Z" level="error" msg="Handler for POST /containers/{name:.*}/start returned error: Cannot start container 431093d71d60110a3dd250dcc5966abd625b5f5a7fc9e7766a53aeebb5a23e84: fork/exec /var/lib/rce/init/dockerinit-1.4.1: invalid argument"
Feb 29 21:14:02 basestation rce[20936]: time="2016-02-29T21:14:02Z" level="error" msg="HTTP Error: statusCode=500 Cannot start container 431093d71d60110a3dd250dcc5966abd625b5f5a7fc9e7766a53aeebb5a23e84: fork/exec /var/lib/rce/init/dockerinit-1.4.1: invalid argument"
Feb 29 21:14:02 basestation systemd1: resin-supervisor.service: main process exited, code=exited, status=1/FAILURE
Feb 29 21:14:02 basestation bash[12598]: time="2016-02-29T21:14:02Z" level="fatal" msg="Error response from daemon: Cannot start container 431093d71d60110a3dd250dcc5966abd625b5f5a7fc9e7766a53aeebb5a23e84: fork/exec /var/lib/rce/init/dockerinit-1.4.1: invalid argument"
Feb 29 21:14:02 basestation rce[20936]: time="2016-02-29T21:14:02Z" level="info" msg="-job attach(431093d71d60110a3dd250dcc5966abd625b5f5a7fc9e7766a53aeebb5a23e84) = OK (0)"
Feb 29 21:14:02 basestation rce[20936]: time="2016-02-29T21:14:02Z" level="info" msg="POST /v1.16/containers/resin_supervisor/stop?t=10"
Feb 29 21:14:02 basestation rce[20936]: time="2016-02-29T21:14:02Z" level="info" msg="+job stop(resin_supervisor)"
Feb 29 21:14:02 basestation rce[20936]: Container already stopped
Feb 29 21:14:02 basestation rce[20936]: time="2016-02-29T21:14:02Z" level="info" msg="-job stop(resin_supervisor) = ERR (1)"
Feb 29 21:14:02 basestation rce[12629]: resin_supervisor
Feb 29 21:14:03 basestation rce[20936]: time="2016-02-29T21:14:03Z" level="info" msg="DELETE /v1.16/contai
Pablo Carranza Vélez
@pcarranzav
Feb 29 2016 21:18
hmm okay, that's a new one
dlarm
@dlarm
Feb 29 2016 21:18
/var/log/supervisor-log/ is an empty directly
directory even
Pablo Carranza Vélez
@pcarranzav
Feb 29 2016 21:18
does your image have any changes compared to the standard resin one? did you change kernel or sth like that?
dlarm
@dlarm
Feb 29 2016 21:19
plenty of kernel differences and software packages required for our hardware
Pablo Carranza Vélez
@pcarranzav
Feb 29 2016 21:20
could be a kernel version incompatibility then (docker/docker#9702)
(@agherzan @petrosagg any ideas?)
could you post uname -a please @dlarm ?
dlarm
@dlarm
Feb 29 2016 21:22
this is running 4.1
our other hardware has 3.14
I'll have to see if I can get lxc-checkconfig on there to make sure I'm not missing anything
Linux basestation 4.1.2-fslc+g95d9e15 #1 SMP PREEMPT Tue Feb 23 16:58:30 PST 2016 armv7l GNU/Linux
Pablo Carranza Vélez
@pcarranzav
Feb 29 2016 21:24
yeah I was about to suggest that
dlarm
@dlarm
Feb 29 2016 21:25
let me double check your kernel options for rce are there
Pablo Carranza Vélez
@pcarranzav
Feb 29 2016 21:26
dlarm
@dlarm
Feb 29 2016 23:53
@pcarranzav So it was definitely my kernel options. I added in the additional cgroups and namespace settings and appear to be in business