[ell-i-developers] Re: Robot Framework Docker Images

  • From: Asif Sardar <engr.asif.sardar@xxxxxxxxxxxxxx>
  • To: Eero Hakala <eero.k.hakala@xxxxxxxxx>
  • Date: Fri, 20 Feb 2015 19:21:38 +0200

Hi all,

RIOT is also added to the docker image (elli/robotframework) /home/RIOT.
The hello_world in examples folder compiles and run, but some reason the
networking part is not working, the bridge-utils is also installed, but it
does not create tun/tap devices. There seems to be a clash between docker's
image networking configuration and the RIOT tun/tap shell script. The
bridge doesn't get made ...

The dockerfile is located at
https://github.com/asifsardar26/Runtime/blob/feature-encX24J600-wip/Dockerfile

On Fri, Feb 20, 2015 at 4:16 PM, Asif Sardar <
engr.asif.sardar@xxxxxxxxxxxxxx> wrote:

> Hi Eero,
>
> The gcc-arm-none-eabi binaries are now added to the coontainer, the
> dockerfile is also updated in the repository.
>
> Moreover, I will update the docker file to also add RIOT support. I will
> test if it works in the environment!
>
> I am also working on how linking the two containers to communicate with
> eachother, with regard to remotelibrary in robotframework.
>
> On Fri, Feb 20, 2015 at 2:28 PM, Asif Sardar <
> engr.asif.sardar@xxxxxxxxxxxxxx> wrote:
>
>> Hello Eero,
>>
>> Please use the image elli/robotframework which is automated and can be
>> linked with git repositories ...
>>
>> It will be very good that in near future we have one master branch which
>> merges all these working branches (Ivan can you do that with permission of
>> Pekka?)
>>
>> Then anyone who commits to that git, the docker image will be
>> automatically built!
>>
>>
>> On Fri, Feb 20, 2015 at 2:17 PM, Eero Hakala <eero.k.hakala@xxxxxxxxx>
>> wrote:
>>
>>> Hi all, copied both Ell-i's and Ivan's runtime into Asif's docker
>>> container and both got it compiled without errors and even the emulator
>>> runs in both environments in docker (that again runs in  windows!!!).
>>>
>>> Next I'll clone RIOT environment into this same container!
>>>
>>>
>>> -eero-
>>>
>>>
>>> On Thu, Feb 19, 2015 at 9:41 PM, Eero Hakala <eero.k.hakala@xxxxxxxxx>
>>> wrote:
>>>
>>>> Hi Asif, if you add the arm-none-eabi to Dockerfile,
>>>>
>>>> RUN apt-get update && apt-get install -y \
>>>>         make \
>>>>         gcc \
>>>>         g++ \
>>>>         git \
>>>>         python2.7 \
>>>>         python2.7-dev \
>>>>         python-setuptools \
>>>>         gcc-arm-none-eabi
>>>>
>>>> then it compiles (in windows :), with make from stm32/build directory -
>>>> save the emulator!
>>>>
>>>> g++ -m32 -march=i386 -m32 -march=i386 -Xlinker -export-dynamic -o
>>>> sketch  main.o sketch.o ellduino.o libSPI.a "-L."
>>>> "-L/home/Runtime/stm32/build/../variants/ellduino" "-lsystem_ellduino"
>>>> -L/usr/lib/python2.7/ -L/lib/i386-linux-gnu/ -L/lib32 -L/usr/lib32
>>>> -lpython2.7 -lpthread -ldl -lutil -lm -lstdc++
>>>> ./libsystem_ellduino.a(system_init.o): In function
>>>> `SystemInitPeripherals':
>>>> /home/Runtime/stm32/build/../system/stm32/src/system_init.c:132:
>>>> undefined reference to `__peripheral_start'
>>>> /home/Runtime/stm32/build/../system/stm32/src/system_init.c:132:
>>>> undefined reference to `__peripheral_end'
>>>>
>>>>
>>>>
>>>> -eero-
>>>>
>>>>
>>>>
>>>> On Thu, Feb 19, 2015 at 3:47 PM, Asif Sardar <
>>>> engr.asif.sardar@xxxxxxxxxxxxxx> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> If you have docker installed in your laptops, you would only need to
>>>>> pull one of the following docker images to check the Ell-i robot framework
>>>>> testing environment.
>>>>>
>>>>> - asifsardar26/elli-robotframework-64bit
>>>>> - asifsardar26/elli-robotframework-32bit
>>>>> - elli/robotframework
>>>>>
>>>>> e.g.
>>>>>
>>>>> sudo docker pull elli/robotframework
>>>>>
>>>>> Then
>>>>>
>>>>> sudo docker run -it elli/robotframework
>>>>>
>>>>> Moreover, the dockerfiles for the above images has been committed to
>>>>> the following repository:
>>>>>
>>>>> https://github.com/asifsardar26/Runtime/tree/feature-encX24J600-wip
>>>>>
>>>>> The image (elli/robotframework) is built using 32bit/ubuntu base
>>>>> image, it can be automatically triggered by any changes to the above
>>>>> repository to build the latest image.
>>>>>
>>>>> For example, if I do enhancements to test suites and test scripts and
>>>>> commit these changes to the above repository, this commit will trigger my
>>>>> docker hub repository and start building the latest image!
>>>>>
>>>>> The other images (asifsardar26/elli-robotframework-64bit &
>>>>> asifsardar26/elli-robotframework-32bit) are not build automated, those 
>>>>> were
>>>>> built and pushed to docker hub for experimenting the "Dockerfile" and
>>>>> docker hub repositories.
>>>>>
>>>>> --
>>>>>
>>>>>
>>>>>
>>>>> *With Best Regards,Asif Sardar.+358 43 8265795 <%2B358%2043%208265795>*
>>>>>
>>>>
>>>>
>>>
>>
>>
>> --
>>
>>
>>
>> *With Best Regards,Asif Sardar.+358 43 8265795 <%2B358%2043%208265795>*
>>
>
>
>
> --
>
>
>
> *With Best Regards,Asif Sardar.+358 43 8265795 <%2B358%2043%208265795>*
>



-- 



*With Best Regards,Asif Sardar.+358 43 8265795*

Other related posts: