https://devzone.nordicsemi.com/f/nordic-q-a/126341/using-ncs-docker-image-with-jlinkHi devzone, I am starting to write some tests for my application, and I have a couple questions/remarks about the provided Docker image. Link to documentation . 1/ The first few tests I have written are done using the native_sim board. When I wanten-USTelligent Community 13Fri, 02 Jan 2026 12:43:12 GMThttps://devzone.nordicsemi.com/thread/557813?ContentTypeID=1Fri, 02 Jan 2026 12:43:12 GMT137ad170-7792-4731-bb38-c0d22fbe4515:c53ae9c4-ef2d-46c1-9843-3a33120545aajoh<p>Hi Nicolas,</p> <p><strong>Question 1: Compiling<br /></strong><br />You&#39;re correct, `gcc` is not installed and thus native_sim targets won&#39;t compile. When compiling against a non sim board (such as&nbsp;nrf54lm20dk/nrf54lm20a/cpuapp), it works, because the zephyr-arm variant of GCC is installed at /opt/ncs/toolchains/f911d4f4e7/opt/zephyr-sdk/arm-zephyr-eabi/bin.<br /><br />I&#39;ll let the relevant team know of this issue. At the moment, the best workaround, as you say, is probably to either<br /><br />A: Manually install gcc and gcc-multilib each time<br />B: Create your own docker image based on&nbsp;ghcr.io/nrfconnect/sdk-nrf-toolchain<br /><br /></p> <p><strong>Question 2: J-Link error</strong></p> <p>This error is somewhat misleading. It&#39;s able to install JLink and then complains it can&#39;t reload the udev rules. Even though this error is printed, the JLink binaries are there and working (although the installation is in an error state). You can attempt this with `nrfutil device list` to see your connected devices. If JLink is not installed, it&#39;ll also print a warning.&nbsp;<br /><br />I think this is a bug, I&#39;ll let the team know.</p><div style="clear:both;"></div>