Bug 926187 – net-misc/gns3-server-2.2.45 - starting docker containers fails with: exec /gns3/init.sh: no such file or directory

• Status: UNCONFIRMED
• Product: Gentoo Linux

[Description Krystof Pistek 2024-03-05 09:26:45 UTC]

Created attachment 886732 [details]
emerge --info gns3-server busybox

Upon attempting to start some (most?) docker containers (tested with Chromium and Mikrotik WinBox guests), the gns3server process encounters the following error:

`ERROR docker_vm.py:498 exec /gns3/init.sh: no such file or directory`

The GUI only reports the latter part of the error, `exec /gns3/init.sh: no such file or directory`.

I have first encountered this bug in net-misc/gns3-server-2.2.43, and it is present in net-misc/gns3-server-2.2.45 today. I do not know when it first appeared. The cause is line 58 in the ebuild:

`ln -s /bin/busybox "${D}$(python_get_sitedir)/gns3server/compute/docker/resources/bin/busybox" || die`

This creates a symlink pointing to the system /bin/busybox. When creating a docker guest, "$(python_get_sitedir)/gns3server/compute/docker/resources" gets used as a volume and is bind-mounted to the container's /gns3 directory.

When starting the container, the entrypoint /gns3/init.sh gets executed, which lists the interpreter /gns3/bin/busybox, i.e. the symlink still pointing to the path /bin/busybox. If the container does not contain such a file, the above error is produced.

Replacing the symlink "$(python_get_sitedir)/gns3server/compute/docker/resources/bin/busybox" with a copy of /bin/busybox resolves the issue.

[Comment 1 mphi 2024-03-30 12:55:56 UTC]

(In reply to Krystof Pistek from comment #0)
> Created attachment 886732 [details]
> emerge --info gns3-server busybox
> 
> Upon attempting to start some (most?) docker containers (tested with
> Chromium and Mikrotik WinBox guests), the gns3server process encounters the
> following error:
> 
> `ERROR docker_vm.py:498 exec /gns3/init.sh: no such file or directory`
> 
> The GUI only reports the latter part of the error, `exec /gns3/init.sh: no
> such file or directory`.
> 
> I have first encountered this bug in net-misc/gns3-server-2.2.43, and it is
> present in net-misc/gns3-server-2.2.45 today. I do not know when it first
> appeared. The cause is line 58 in the ebuild:
> 
> `ln -s /bin/busybox
> "${D}$(python_get_sitedir)/gns3server/compute/docker/resources/bin/busybox"
> || die`
> 
> This creates a symlink pointing to the system /bin/busybox. When creating a
> docker guest, "$(python_get_sitedir)/gns3server/compute/docker/resources"
> gets used as a volume and is bind-mounted to the container's /gns3 directory.
> 
> When starting the container, the entrypoint /gns3/init.sh gets executed,
> which lists the interpreter /gns3/bin/busybox, i.e. the symlink still
> pointing to the path /bin/busybox. If the container does not contain such a
> file, the above error is produced.
> 
> Replacing the symlink
> "$(python_get_sitedir)/gns3server/compute/docker/resources/bin/busybox" with
> a copy of /bin/busybox resolves the issue.

I have the same problem.
Your workaround of replacing the busybox symlink worked for me.
Thank you.