<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Using npm:Install with Image-based Services doesn&#x27;t work]]></title><description><![CDATA[<p dir="auto">Hi <a class="plugin-mentions-group plugin-mentions-a" href="/groups/inedo-engineer" aria-label="Profile: inedo-engineer">@<bdi>inedo-engineer</bdi></a>,<br />
I'm starting to set up Image-based Services to keep from having to have so many things installed on the build server.  This is working great for the .NET builds but when I tried to use it for npm::Install I ran into a problem.  Apparently when you activate Imaged-based Services for npm::Install it tries to execute at the root of the container which fails with <em>Tracker "idealTree" already exists</em>.  According to my research when you the <em>docker run</em> command you need an additional argument of <em>"&lt;workdir&gt;:/var/buildmaster-ibs"</em> but I'm not sure how to do that with your software.  I was hoping someone could give me instructions or maybe report this as a bug to be fixed.</p>
<p dir="auto">Thank you,<br />
Brandon</p>
]]></description><link>https://forums.inedo.com/topic/5847/using-npm-install-with-image-based-services-doesn-t-work</link><generator>RSS for Node</generator><lastBuildDate>Sat, 03 Oct 2026 22:41:14 GMT</lastBuildDate><atom:link href="https://forums.inedo.com/topic/5847.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 03 Oct 2026 04:33:58 GMT</pubDate><ttl>60</ttl></channel></rss>