Skip to content
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 console into custom component #383

Closed
mbrodala opened this issue Feb 23, 2017 · 1 comment · Fixed by #385
Closed

Cannot console into custom component #383

mbrodala opened this issue Feb 23, 2017 · 1 comment · Fixed by #385
Assignees

Comments

@mbrodala
Copy link
Contributor

While it is possible to add arbitrary Docker images as custom components (see #365), you cannot console into these since the user gonano does not exist:

λ nanobox console local data.custom


                                   **
                                ********
                             ***************
                          *********************
                            *****************
                          ::    *********    ::
                             ::    ***    ::
                           ++   :::   :::   ++
                              ++   :::   ++
                                 ++   ++
                                    +
                    _  _ ____ _  _ ____ ___  ____ _  _
                    |\ | |__| |\ | |  | |__) |  |  \/
                    | \| |  | | \| |__| |__) |__| _/\_

--------------------------------------------------------------------------------
+ You are in a Linux container
+ Your local source code has been mounted into the container
+ Changes to your code in either the container or desktop will be mirrored
+ If you run a server, access it at >>
--------------------------------------------------------------------------------

unable to find user gonano: no matching entries in passwd file

It makes perfect sense since these images where not customized for usage with Nanobox. However I wonder if Nanobox could provide a fallback in cases like these, e.g. connect as root instead or similar.

@mbrodala
Copy link
Contributor Author

mbrodala commented Feb 24, 2017

λ nanobox console local data.custom -u root


                                   **
                                ********
                             ***************
                          *********************
                            *****************
                          ::    *********    ::
                             ::    ***    ::
                           ++   :::   :::   ++
                              ++   :::   ++
                                 ++   ++
                                    +
                    _  _ ____ _  _ ____ ___  ____ _  _
                    |\ | |__| |\ | |  | |__) |  |  \/
                    | \| |  | | \| |__| |__) |__| _/\_

--------------------------------------------------------------------------------
+ You are in a Linux container
+ Your local source code has been mounted into the container
+ Changes to your code in either the container or desktop will be mirrored
+ If you run a server, access it at >>
--------------------------------------------------------------------------------

mesg: ttyname failed: Success
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

root@a75dd7f37c49:/#

Works like a charm, thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants