<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Is running OpenCL in multiple Docker containers problematic? in OpenCL* for CPU</title>
    <link>https://community.intel.com/t5/OpenCL-for-CPU/Is-running-OpenCL-in-multiple-Docker-containers-problematic/m-p/1167091#M6441</link>
    <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;We have some issues running multiple instances of our CNN-pipeline in separated Docker containers. The Linux randomly enters a "Zombie" state (no reaction to anything, even to the "Magic SysRq keys" and so much network traffic that every device on the next switch is down). (see &lt;A href="https://software.intel.com/en-us/forums/opencl/topic/804936"&gt;https://software.intel.com/en-us/forums/opencl/topic/804936).&lt;/A&gt;&lt;/P&gt;&lt;P&gt;As the problems started when updating the OpenCL driver and only occurred (until now) when multiple Docker containers with OpenCL were running, there might be a multiprocessing issue with the OpenCL driver when used within separated Docker containers (some tests running native (not in Docker containers) caused no problems, but this might just be a coincidence as the tests where only done for a few hours).&lt;/P&gt;&lt;P&gt;So our question is how multiprocessing is handled by the driver and if we need to add more than just the /dev/dri device to the Docker containers to avoid race conditions between the different docker containers.&lt;/P&gt;&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;Thomas&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 10:09:04 GMT</pubDate>
    <dc:creator>Senfter__Thomas</dc:creator>
    <dc:date>2019-03-11T10:09:04Z</dc:date>
    <item>
      <title>Is running OpenCL in multiple Docker containers problematic?</title>
      <link>https://community.intel.com/t5/OpenCL-for-CPU/Is-running-OpenCL-in-multiple-Docker-containers-problematic/m-p/1167091#M6441</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;We have some issues running multiple instances of our CNN-pipeline in separated Docker containers. The Linux randomly enters a "Zombie" state (no reaction to anything, even to the "Magic SysRq keys" and so much network traffic that every device on the next switch is down). (see &lt;A href="https://software.intel.com/en-us/forums/opencl/topic/804936"&gt;https://software.intel.com/en-us/forums/opencl/topic/804936).&lt;/A&gt;&lt;/P&gt;&lt;P&gt;As the problems started when updating the OpenCL driver and only occurred (until now) when multiple Docker containers with OpenCL were running, there might be a multiprocessing issue with the OpenCL driver when used within separated Docker containers (some tests running native (not in Docker containers) caused no problems, but this might just be a coincidence as the tests where only done for a few hours).&lt;/P&gt;&lt;P&gt;So our question is how multiprocessing is handled by the driver and if we need to add more than just the /dev/dri device to the Docker containers to avoid race conditions between the different docker containers.&lt;/P&gt;&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;Thomas&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 10:09:04 GMT</pubDate>
      <guid>https://community.intel.com/t5/OpenCL-for-CPU/Is-running-OpenCL-in-multiple-Docker-containers-problematic/m-p/1167091#M6441</guid>
      <dc:creator>Senfter__Thomas</dc:creator>
      <dc:date>2019-03-11T10:09:04Z</dc:date>
    </item>
  </channel>
</rss>

