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

Initial CA setup fails on Windows #878

Open
dustinleblanc opened this Issue Apr 9, 2018 · 3 comments

Comments

Projects
None yet
4 participants
@dustinleblanc
Member

dustinleblanc commented Apr 9, 2018

Fresh Windows 10 install, Running from master with Git Bash

capture

@dustinleblanc dustinleblanc added the bug label Apr 9, 2018

@dustinleblanc dustinleblanc added this to the 3.0.0-beta.41 milestone Apr 9, 2018

@dustinleblanc dustinleblanc self-assigned this Apr 22, 2018

@pirog pirog removed this from the 3.0.0-beta.41 milestone Apr 30, 2018

@fafnirical

This comment has been minimized.

fafnirical commented May 16, 2018

Getting the same with Lando v3.0.0-beta.44 on Windows 10.

@dustinleblanc

This comment has been minimized.

Member

dustinleblanc commented May 17, 2018

Thanks @fafnirical, we'll keep this in the backlog and hopefully fix it when we finish up some more of the CA trusting magic

@aaronlsilber

This comment has been minimized.

aaronlsilber commented May 24, 2018

FYI, here's my experience with this issue.

Nuked Docker and Lando on Windows after #971. Reinstalled both through Lando (beta 45) executable. Ran lando start with .lando.yml;

name: supercoolwebsite-com
recipe: drupal7
config:
  webroot: .
  via: nginx

services:
  node:
    type: node:6.11
    run: 
      - "cd $LANDO_MOUNT && npm install"
      - "cd $LANDO_MOUNT && grunt"
    globals:
      grunt-cli: "latest"
      bower: "latest"
      ruby: "latest"
      sass: "latest"

tooling:
  npm:
    service: node
  node:
    service: node
  bower:
    service: node
  grunt:
    service: node

Logged:

Creating network "landocasetupkenobi38ahsoka9d80c383cd3e777e7730167e14a2c0f4b73727cb_default" with the default driverPulling ca (devwithlando/util:stable)...
Creating landocasetupkenobi38ahsoka9d80c383cd3e777e7730167e14a2c0f4b73727cb_ca_1 ... done
Looks like you do not have a Lando CA yet! Let's set one up!
Trying to setup root CA with...
LANDO_CA_CERT: lando.pem
LANDO_CA_KEY: lando.key
CA_CERT: /certs/lando.pem
CA_KEY: /certs/lando.key
/certs/lando.pem not found... generating one
Generating RSA private key, 2048 bit long modulus
....+++
..........+++
e is 65537 (0x10001)
/certs/lando.pem not found... generating one
CA generated at /certs/lando.pem
ERROR: No such service: /bin/sh
ERROR: No such service: /bin/sh
ERROR: No such service: /bin/sh
ERROR: No such service: /bin/sh
ERROR: No such service: /bin/sh
warn: Something is wrong with the proxy! {}
warn: Trying to take corrective action...
Creating network "landoproxyhyperion5000gandalfedition_edge" with driver "bridge"
Pulling proxy (traefik:1.5.4-alpine)...
Creating landoproxyhyperion5000gandalfedition_proxy_1 ... done
Creating network "xxxxxxxxxxxxxx_default" with the default driver
Creating volume "xxxxxxxxxxxxxx_data" with default driver
Creating volume "xxxxxxxxxxxxxx_appserver" with default driver
Creating volume "xxxxxxxxxxxxxx_data_database" with default driver
Pulling node (node:6.11)...
Pulling database (mysql:5.7)...
Pulling appserver (devwithlando/php:7.0-fpm)...
Pulling nginx (nginx:latest)...
Creating xxxxxxxxxxxxxx_database_1  ... done
Creating xxxxxxxxxxxxxx_appserver_1 ... done
Creating xxxxxxxxxxxxxx_node_1      ... done
Creating xxxxxxxxxxxxxx_nginx_1     ... done
Waiting until nginx service is ready...
Waiting until appserver service is ready...
Waiting until database service is ready...
Waiting until node service is ready...
Waiting until nginx service is ready...
Waiting until database service is ready...
Waiting until nginx service is ready...
Waiting until database service is ready...
Waiting until nginx service is ready...
Waiting until database service is ready...
Waiting until nginx service is ready...
Waiting until nginx service is ready...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   599    0   599    0     0   1031      0 --:--:-- --:--:-- --:--:--  1030
100 4482k  100 4482k    0     0  1288k      0  0:00:03  0:00:03 --:--:-- 1944k
 PHP configuration      :
 PHP OS                 :  Linux
 Drush script           :  /tmp/drush.phar
 Drush version          :  8.1.16
 Drush temp directory   :  /tmp
 Drush configuration    :
 Drush alias files      :

/usr/local/bin/sass -> /usr/local/lib/node_modules/sass/sass.js
/usr/local/lib
`-- sass@1.3.2

/usr/local/lib
`-- ruby@0.6.1
  `-- lodash@4.17.10

/usr/local/bin/bower -> /usr/local/lib/node_modules/bower/bin/bower
/usr/local/lib
`-- bower@1.8.4

/usr/local/bin/grunt -> /usr/local/lib/node_modules/grunt-cli/bin/grunt
/usr/local/lib
`-- grunt-cli@1.2.0
  +-- findup-sync@0.3.0
  | `-- glob@5.0.15
  |   +-- inflight@1.0.6
  |   | `-- wrappy@1.0.2
  |   +-- inherits@2.0.3
  |   +-- minimatch@3.0.4
  |   | `-- brace-expansion@1.1.11
  |   |   +-- balanced-match@1.0.0
  |   |   `-- concat-map@0.0.1
  |   +-- once@1.4.0
  |   `-- path-is-absolute@1.0.1
  +-- grunt-known-options@1.1.0
  +-- nopt@3.0.6
  | `-- abbrev@1.1.1
  `-- resolve@1.1.7

npm WARN enoent ENOENT: no such file or directory, open '/app/package.json'
npm WARN app No description
npm WARN app No repository field.
npm WARN app No README data
npm WARN app No license field.
grunt-cli: The grunt command line interface (v1.2.0)

Fatal error: Unable to find local grunt.

If you're seeing this message, grunt hasn't been installed locally to
your project. For more information about installing and configuring grunt,
please see the Getting Started guide:

http://gruntjs.com/getting-started
error: Looks like one of your build steps failed...
warn: This **MAY** prevent your app from working
warn: Check for errors above, fix them, and try again

BOOMSHAKALAKA!!!

Your app has started up correctly.
Here are some vitals:

Appears to have worked through the errors on it's own.

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