Pierre Rioux
Pierre Rioux
If there is no other method than "docker login" with a password on the command-line, I'm not even sure I want such a feature in CBRAIN. It is a terrible...
I think until there is a better mechanism on the docker side, CBRAIN should only allow public docker image. If your image is not public, too bad...
The problem is that CBRAIN is entrusted with the dockerhub credentials of an ordinary CBRAIN user. The username and password of that user on dockerhub kept in plain text within...
Okay, that makes things clearer. Now that thing is, cbrain doesn't have a user on dockerhub. Maybe we should create one? (I assume that's what you meant by `grant access...
I haven't worked on this, no, but it's feasible for sure. I'm just wondering where we put the docker username and password... in the ToolConfig object? In the Tool object?...
Hum, I see. Yes, if of course I was thinking of the reverse situation again, but we only need one account. Ok, seems feasible. It will be ready in June...
Also, I think we should try for a public image first, and then if it fails log in and try to see if it's accessible.
Wee need a singleton object in CBRAIN that represent the entire CBRAIN installation; I have used in the past the first BrainPortal object, but that's not necessarily the best place,...
It would be a great place to store global information about the entire system, including the docker hub credentials.