Docker: Issueshttps://projects.theforeman.org/https://projects.theforeman.org/favicon.ico?16970236342015-02-04T09:00:24ZForeman
Redmine Feature #9217 (Closed): DNS and containerhttps://projects.theforeman.org/issues/92172015-02-04T09:00:24ZFlorent Delvailleflorent.delvaille@gmail.com
<p>Hello,</p>
<p>It would be nice to have a possibility to create DNS for a specific container.</p>
<p>The feature request basically comes from an idea we had for our organization:<br />- 1 Big VM (Vcenter) called ldv-<application><br />- x containers, each of them being based on <application>, and end in X times ldv-<application>01 … X.</p>
<p>This will ease the access to developers/tester/etc …</p>
<p>Regards;</p> Bug #8789 (Closed): Wrong link for "learn more about cpu shares" in configuration step of new con...https://projects.theforeman.org/issues/87892014-12-23T20:41:46ZVanya Jauhalvanyajauhal1995@gmail.com
<p>In the configuration step of a New Container the "learn more about cpu shares" links to <a class="external" href="http://docs.fedoraproject.org/en-US/Fedora/17/html/Resource_Management_Guide/sec-cpuset">http://docs.fedoraproject.org/en-US/Fedora/17/html/Resource_Management_Guide/sec-cpuset</a>.</p>
<p>But this page does not have any explanation about CPU shares.</p> Feature #7865 (Closed): Containers should be started with DNS optionshttps://projects.theforeman.org/issues/78652014-10-09T06:54:52ZDaniel Lobato Garciaelobatocs@gmail.com
<p>Either the wizard, or the start button should display some info to set up DNS in the container. Format is:</p>
<pre>
{ "DNS" : ["192.168.121.1", "8.8.8.8"] }
</pre>
<p>Order does not matter for most ns implementations.</p> Feature #7864 (Closed): Exposed ports supporthttps://projects.theforeman.org/issues/78642014-10-09T06:52:05ZDaniel Lobato Garciaelobatocs@gmail.com
<p>The configuration or environment part of the wizard should show a way of adding exposed ports. The Docker Remote API supports it but Fog doesn't yet. Assume Fog does support it as I have a patch pending review.<br />The format for exposed ports goes like<br /><pre>
{ "ExposedPorts" : [ "22/tcp": {}, "80/tcp": {}] }
</pre></p>
<p>Yes, key is the port/protocol, value is.. nothing?</p>