Yes. Exactly what I meant. I suspect the environment variables will also change with the new Docker that is in beta testing. I have not had time to test it yet.
IMHO, on startup we should check if Docker is running and if so connect to either the "default" machine or one which is defined in Preferences or Properties (persistent storage of some kind) or as Roland mentioned, configurable through an extension point. If Docker isn't running, we should throw up a dialog that asks the user if we should try to launch it. If not found we could even <cough> try to install it with vagrant or point them to the Docker website.
In our case, we are hosting cross-toolchains in containers, so as soon as the C/C++ perspective is active (or our specific plugin) we would want the docker machine in question to be connected. As invisible to the user as possible :)
I am happy to try to contribute to the code base.
Cheers.
--Tim (Intel)
_______________________________________________
linuxtools-dev mailing list
linuxtools-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/linuxtools-dev