Jeremy Grossmann

> An interim solution, line 367 was commented out and the container starts as expected Do you see the volume after you started the container from GNS3?

The interfaces are set up by the `/gns3/init.sh` script that should be in that volume. After commenting line 367, do you confirm you see the `/gns3/init.sh` script inside the container?...

@rcanonico thanks for this info. What container to you use to reproduce the issue?

I have added a change for this in v2.2.34: https://github.com/GNS3/gns3-server/commit/129f0a631c0916d5fb9db8d00675f392d5a28636 Do you have the same issue using v2.2.34?

Sorry, you are right, that fix is not for this issue. We haven't found how to fix it yet.

Thanks for bridging this to our attention, definitely something we should try to mitigate as much as we can :+1:

This should have been fixed with version 2.2. Please comment back if you see the same issue in version 2.2.x or later. Thanks.

I meant version 2.2 or later. Thanks.

Can you reproduce this with any Qemu node? How long do you have to wait for it to happen?

@1001QAdotNET is there a chance your system went to sleep mode?