You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
λ 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:/#
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: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.The text was updated successfully, but these errors were encountered: