These are chat archives for resin-io/chat

11th
Jul 2017
Daniele Riccucci
@devster31
Jul 11 2017 11:48
hello, I'm joining because I really liked this article: https://resin.io/blog/building-arm-containers-on-any-x86-machine-even-dockerhub/ Now I'm curious to know if this is just a matter of copying the necessary binaries into a different container. For example, I like linuxserver.io containers because of their s6-overlay, would I be able to build an image on docker hub using their base image and your binaries for cross-build-start and end?
Thibaut Diseur
@kewwwa
Jul 11 2017 13:04
Hello, how could I suggest features ?
Shaun Mulligan
@shaunmulligan
Jul 11 2017 13:08
@kewwwa you can suggest them here, but probably forums.resin.io is the best place
Thibaut Diseur
@kewwwa
Jul 11 2017 13:24
Ok maybe we can discuss here if it's a good idea or not
#1 : upload a splash screen into resinos for future downloads, to avoid modifying img each time we download it
Vijay Sharma
@Eulerianial
Jul 11 2017 13:58
Dear all, I have to convert this command docker run --name=domoticz \ --privileged \ --cidfile="cid" \ -d \ -p 8080:8080 \ -t
for resin.io
I first installed the docker image of the domoticz as: FROM Domotic-Docker-Image
but how do I issue the docker run command after installing the base image
I want to convert specificially the above command: docker run --name=domoticz \ --privileged \ --cidfile="cid" \ -d \ -p 8080:8080 \ -t
Shaun Mulligan
@shaunmulligan
Jul 11 2017 14:03
you should be able to just push a dockerfile with FROM Domotic-Docker-Image in it and it should work, since resin.io containers run with --privileged and --net=host so your port 8080 will be exposed locally. you can actually also reach it from anywhere using http://<UUID>.resindevice.io:8080
Vijay Sharma
@Eulerianial
Jul 11 2017 14:03
Shaun I did that
but then when I try to enable the public URL it throws error
For reference this is my public URL https://9edf6ee73396d218001bbbb01bcca682.resindevice.io/
In the logs I am seeing following errors:
Shaun Mulligan
@shaunmulligan
Jul 11 2017 14:05
@Eulerianial you need to use this url: http://9edf6ee73396d218001bbbb01bcca682.resindevice.io:8080/
Vijay Sharma
@Eulerianial
Jul 11 2017 14:06
ahh! I got it
Shaun Mulligan
@shaunmulligan
Jul 11 2017 14:06
basically the device exposes 2 port, port 80 over https and port 8080 over http. so you need to use the latter, or make domotics bind to port 80
Vijay Sharma
@Eulerianial
Jul 11 2017 14:06
also in my terminal log I see the following errors:
06.07.17 16:45:43 (+0200) 2017-07-06 09:45:43.441 Domoticz V3.6959 (c)2012-2017
GizMoCuz
06.07.17 16:45:43 (+0200) 2017-07-06 09:45:43.441 Build Hash: 16cba568-modified
, Date: 2017-03-15 06:21:36
06.07.17 16:45:43 (+0200) 2017-07-06 09:45:43.443 System: Raspberry Pi
06.07.17 16:45:43 (+0200) 2017-07-06 09:45:43.444 Startup Path: /src/domoticz/
06.07.17 16:45:44 (+0200) 2017-07-06 09:45:44.030 PluginSystem: Started, Python
version '3.5.3'.
06.07.17 16:45:44 (+0200) 2017-07-06 09:45:44.036 Active notification Subsystem
s: gcm, http (2/12)
06.07.17 16:45:44 (+0200) 2017-07-06 09:45:44.059 WebServer(HTTP) started on ad
dress: :: with port 8080
06.07.17 16:45:44 (+0200) 2017-07-06 09:45:44.085 Error: WebServer(SSL) startup
failed on address 0.0.0.0 with port: 443: use_certificate_chain_file: No such f
ile or directory
06.07.17 16:45:44 (+0200) 2017-07-06 09:45:44.085 Error: WebServer(SSL) check p
rivileges for opening ports below 1024
06.07.17 16:45:44 (+0200) 2017-07-06 09:45:44.086 Proxymanager started.
06.07.17 16:45:44 (+0200) 2017-07-06 09:45:44.087 Starting shared server on: ::
:6144
06.07.17 16:45:44 (+0200) 2017-07-06 09:45:44.088 TCPServer: shared server star
ted...
06.07.17 16:45:44 (+0200) 2017-07-06 09:45:44.088 RxQueue: queue worker started...
11.07.17 15:32:20 (+0200) 2017-07-11 08:32:20.032 EventSystem: reset all events...
11.07.17 15:32:20 (+0200) 2017-07-11 08:32:20.033 EventSystem: reset all device statuses...
11.07.17 15:32:20 (+0200) 2017-07-11 08:32:20.034 EventSystem: Started
11.07.17 15:32:20 (+0200) 2017-07-11 08:32:20.530 PluginSystem: Entering work loop.
11.07.17 15:32:27 (+0200) Application is already running 'registry2.resin.io/rasbianjessie/14b62dc08d3522e38f099a75c844342502fb4768'
11.07.17 16:05:11 (+0200) 2017-07-11 09:05:11.639 Incoming connection from: 52.4.252.97
Are these fine?
Shaun Mulligan
@shaunmulligan
Jul 11 2017 14:13
I'm not really familiar with Domotics, but it looks okay. I would just check that all the functionality you need is working
Vijay Sharma
@Eulerianial
Jul 11 2017 14:17
Sure @shaunmulligan
Henry Miskin
@hpgmiskin
Jul 11 2017 16:50
How many threads should I make use of on the build server? make -j?
Gergely Imreh
@imrehg
Jul 11 2017 16:50
@hpgmiskin which device type are you building for?
Henry Miskin
@hpgmiskin
Jul 11 2017 16:51
@imrehg RPi3
Gergely Imreh
@imrehg
Jul 11 2017 16:54
I was quickly checking up on it, it seems that indeed the automatic make -j (without a number) should be probably the right one for you if possible. @hpgmiskin
There are some improvements to our builders on the way as well, which should help further, but is not quite ready yet (not to tease too much)
Henry Miskin
@hpgmiskin
Jul 11 2017 16:56
Thanks Gergely. Was currently using make -j4 as following a tutorial but did not know what would be best for the build server
Cool I look forward to the build server updates. Thanks
Gergely Imreh
@imrehg
Jul 11 2017 16:57
Yeah, try out the -j, and let us know how does it work for you! (it depends on the build job too, of course)
Anton Belodedenko
@ab77
Jul 11 2017 17:26
@resinio guys, any idea where https://forums.resin.io/t/hummingboard-os-update/763 has stalled?
it's still v1.6.0, more or less unusable in the current state
resin.io team
@resinio
Jul 11 2017 19:01
[Florin-Ionut Sarbu (floion)] there are some issues with the graphics @ab77