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

the input device is not a TTY #3395

Open
clacdesdoigts opened this issue May 12, 2022 · 1 comment
Open

the input device is not a TTY #3395

clacdesdoigts opened this issue May 12, 2022 · 1 comment
Labels
bug Something aint working right! stale Issue has been auto-flagged as stale

Comments

@clacdesdoigts
Copy link

Happens while building containers with lando start or lando rebuild, using the Wordpress recipe.
This may prevent Lando from installing tools such as WP CLI interactively

Commands are launched in WSL2 (core version : 5.10.16) on Windows 11, in a Debian 11 (bullseye) distribution.
Lando version : 3.6.5

Here is my Landofile :

name: wordpress
recipe: wordpress
proxy:
  appserver:
    - wordpress.lndo.site
    - espace.wordpress.lndo.site
    - account.wordpress.lndo.site
    - ca.wordpress.lndo.site
config:
  php: "7.3"
  via: apache
  webroot: web
  database: mysql:5.7
  xdebug: true
# Services
services:
  database_admin:
    type: phpmyadmin:5.0
    hosts:
      - database
  mail:
    type: mailhog:v1.0.0
    portforward: true
    hogfrom:
      - appserver

And here is the output of lando rebuild :

user@debian:~/www/wordpress$ lando rebuild
? Are you sure you want to rebuild? Yes
Rising anew like a fire phoenix from the ashes! Rebuilding app...
Killing wordpress_database_1       ... done
Killing wordpress_database_admin_1 ... done
Killing wordpress_mail_1           ... done
Killing wordpress_appserver_1      ... done
Going to remove wordpress_database_1, wordpress_database_admin_1, wordpress_mail_1, wordpress_appserver_1
Removing wordpress_database_1       ... done
Removing wordpress_database_admin_1 ... done
Removing wordpress_mail_1           ... done
Removing wordpress_appserver_1      ... done
Pulling database       ... done
Pulling mail           ... done
Pulling appserver      ... done
Pulling database_admin ... done
mail uses an image, skipping
database uses an image, skipping
database_admin uses an image, skipping
appserver uses an image, skipping
landoproxyhyperion5000gandalfedition_proxy_1 is up-to-date
Creating wordpress_appserver_1 ... done
usermod: no changes
usermod: no changes

the input device is not a TTY.  If you are using mintty, try prefixing the command with 'winpty'
ERROR ==> the input device is not a TTY.  If you are using mintty, try prefixing the command with 'winpty'

Creating wordpress_mail_1           ... done
Creating wordpress_database_1       ... done
Creating wordpress_database_admin_1 ... done
Waiting until database service is ready...
Waiting until database service is ready...
Scanning to determine which services are ready... Please stand by...

  _      __              _           __
 | | /| / /__ ________  (_)__  ___ _/ /
 | |/ |/ / _ `/ __/ _ \/ / _ \/ _ `/_/
 |__/|__/\_,_/_/ /_//_/_/_//_/\_, (_)
                             /___/

Your app started up but we detected some things you may wish to investigate.
These only may be a problem.

Note : running docker run -it hello-world shows no error.
Same with docker.exe run -it hello-world though I have installed docker engine inside WSL and disabled interoperability so Lando should not use the Windows host's docker executable.

Trying to run lando wp after that returns /bin/sh: 1: wp: not found
My workaround has been to install WP CLI manually inside the container, but this issue might not be related to the Wordpress recipe, this is why I am posting it here.

@stale
Copy link

stale bot commented May 22, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions and please check out this if you are wondering why we auto close issues.

@stale stale bot added the stale Issue has been auto-flagged as stale label May 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something aint working right! stale Issue has been auto-flagged as stale
Projects
None yet
Development

No branches or pull requests

0 participants