-
Notifications
You must be signed in to change notification settings - Fork 431
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
Docker integration: Add auxiliary console with docker-exec #1039
Comments
I agree. This mean we need to allocate the aux port by default but it's really simplify the usage of most containers. |
I will need to check if we can attach a websocket to a exec. I'm not sure the documentation is not clear on this topic. |
Here a workaround for local docker usage: Create a shell script
Then create a custom console Now you can use the custom console |
This move the allocation of aux port to the base vm. Also now the free of console port during the close is in the base VM. An aux port is allocated to the docker container but not used for the moment. Ref GNS3/gns3-gui#1039
Hmm the websocket is not yet available: I test and we can not attach to the container using websocket |
I have take a look on the source code. They need to do refactoring before adding this call to the API. I doubt it will arrive fast. I found a solution not something very clean, but it's the best I can do :( I wrap docker exec. But no tty could be allocated. Doc about it: |
Thanks !!! Even when it's not perfect it's a good fallback, when you want to debug a container. Just get those validation error, I assume aux is unknown
|
Validation is fixed |
The console on docker VMs gives you the input/output of the docker container, which is fine.
But for debugging a shell in the running container (docker exec -ti <container-id> sh) would be very helpful. So I suggest to add an auxiliary console to such a docker-exec.
The text was updated successfully, but these errors were encountered: