-
Notifications
You must be signed in to change notification settings - Fork 435
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot Start containers #3569
Comments
Example appliance I have used is ipterm |
Hi epacua. It seems that busybox missed from the latest version, as I cannot find it elsewhere except under |
It seems that finally I found a solution by copy it under /usr/share/gns3/gns3-server/lib/python3.10/site-packages/gns3server/compute/docker/resources/bin and not under /usr/lib/python3.10/site-packages/gns3server/compute/docker/resources/ but again it is strange how it was lost without make any change. |
My guess here is that:
gns3 is installed via apt or any system package manager as it saves files at /usr/share.
while this one appears to be installed via pip. So basically you end up with two copies/installations of gns3. What you did, it appears to me, is you copied a system-installed busybox executable with dynamic libraries to gns3 directory. That won't work because the docker depends on statically-built busybox which does not rely on external libraries. |
Hi epacua, Currently I dont have any installed gns3 through pip, (maybe I did that before many times ago) and indeed I installed gns3 via apt package manager. In any case, its strange why the busybox disappeared, even from the correct path after the upgrade. |
switching those package to version 2.2.45 can be ok |
The busybox binary is not included in the GNS3 source code anymore. Busybox must already be installed on your system before trying to start a Docker container. To install on Debian/Ubuntu: On starting a Docker container: the GNS3 server will try to find an executable named "busybox-static", "busybox.static" or "busybox" in the paths listed in the $PATH environment variable, then copy that executable a "resources" user data directory, for instance |
I have updated the error message to explicitly tell that busybox must be installed. |
I recently upgraded to GNS3 2.2.46 and I am no longer able to start any containers that were working previously because of the following error
"error while starting alpine-1: No busybox executable could be found
No busybox executable could be found"
The same behavior faced for all Docker Container templates.
I have tried also to delete them and add them again, without any succeed.
Dont know if its related, but the folder "/usr/lib/python3.10/site-packages/gns3server/compute/docker/resources" is empty.
Please note that this happens only with Docker templates when Dynamips, IOU and Quemu templates run correctly.
Also I can run these docker containers without issues from terminal. Issue happens only when trying to start them inside from GNS3.
Finally busybox is already installed on my system.
Thanks a lot for your assistance.
Panagiotis.
The text was updated successfully, but these errors were encountered: