3 Replies Latest reply on Jan 17, 2017 3:49 PM by Intel Corporation

    Docker container is not running after computer went to sleep

    JelleRoets

      In the new Intel System Studio, to develop and upload programs to my Intel Edison, compilation is now done in a docker container, while the previous Intel devkit eclipse simply cross-compiled the projects.

       

      In order to make sure the docker container is running and eclipse is running with the correct environment variables, you have to startup eclipse using the iss-iot-launcher script.

      However this only works directly after launching this script. If you want to continue using eclipse after your computer was set to sleep or hibernation, I get an error that the docker container isn't running anymore:

      Info: Internal Builder is used for build
      docker exec -i 4eebd24d1c96b20eec34f33307304a5268764b7a96510a27361a224f2fd83b5a /bin/bash -c "cd /workspace/testDwenguino/Debug && i586-poky-linux-g++ -I/usr/include/upm -I/usr/include/mraa -I/workspace/libs -O0 -g3 -Wall -c -fmessage-length=0 --sysroot= -m32 -march=i586 -c -ffunction-sections -fdata-sections -o src/testDwenguino.o ../src/testDwenguino.cpp" 
      Error response from daemon: Container 4eebd24d1c96b20eec34f33307304a5268764b7a96510a27361a224f2fd83b5a is not running
      

       

      How can I easily restart the correct docker container, or make sure it didn't shut down? (I'm currently using Intel System Studio on Mac OSX)

      Currently the only work around is to quit and restart eclipse, which is quite cumbersome. Also note this was not an issue with the former Intel devkit, since it simply didn't use any docker container.