marhan / spring-boot-micrometer-sample

Spring Boot 2 with Micrometer
MIT License
6 stars 4 forks source link

clean install: start_complete_stack.sh ends with sh: vue-cli-service: not found #1

Open jforge opened 5 years ago

jforge commented 5 years ago

A fresh clone on a clean machine lets ./start_complete_stack.sh produce the following output, ending up in a missed vue-cli-service

$ ./start_complete_stack.sh
Creating network "spring-boot-micrometer-sample_monitoring" with driver "bridge"
Creating volume "spring-boot-micrometer-sample_prometheus_data" with default driver
Creating volume "spring-boot-micrometer-sample_grafana_data" with default driver
Creating volume "spring-boot-micrometer-sample_elasticsearch_data" with default driver
Creating volume "spring-boot-micrometer-sample_kibana_data" with default driver
Building elasticsearch
Step 1/1 : FROM docker.elastic.co/elasticsearch/elasticsearch-oss:6.4.0
6.4.0: Pulling from elasticsearch/elasticsearch-oss
256b176beaff: Already exists
6cb472d8b34a: Pull complete
3a4f4d86c1c1: Pull complete
d185a64a7692: Pull complete
bc4d63245d6d: Pull complete
32f4295426b7: Pull complete
b5a86c1368ca: Pull complete
f86a90283ecb: Pull complete
Digest: sha256:20dc93081ec7b5e7111b6982236e9b5384e37ae95dfdbc2227085d29b1505d60
Status: Downloaded newer image for docker.elastic.co/elasticsearch/elasticsearch-oss:6.4.0
 ---> a13ec2fa6275
Successfully built a13ec2fa6275
Successfully tagged spring-boot-micrometer-sample_elasticsearch:latest
Building kibana
Step 1/1 : FROM docker.elastic.co/kibana/kibana-oss:6.4.0
6.4.0: Pulling from kibana/kibana-oss
256b176beaff: Already exists
88643bded09c: Already exists
a5ecb9cf4fd5: Already exists
45199ce6b324: Pull complete
892cfa9b4084: Pull complete
b1dee148358b: Pull complete
f448b4a226da: Pull complete
95f55c641ec9: Pull complete
f612d1f45c31: Pull complete
Digest: sha256:df8ccf5edfc68657fb8e766f780badafdabd854abd5d75e9fa044674e73ceb6f
Status: Downloaded newer image for docker.elastic.co/kibana/kibana-oss:6.4.0
 ---> c8986fcd3caa
Successfully built c8986fcd3caa
Successfully tagged spring-boot-micrometer-sample_kibana:latest
Building springboot
Step 1/6 : FROM openjdk:11-jdk-slim
11-jdk-slim: Pulling from library/openjdk
177e7ef0df69: Already exists
762c9dfbe1b5: Pull complete
0bd3e7cdb759: Pull complete
3b0b10575b21: Pull complete
e1e429842a70: Pull complete
b87db85bb6be: Pull complete
Digest: sha256:2883971188040a03040a0521f9b686293fd8eee13dac5eac402f856db0449f72
Status: Downloaded newer image for openjdk:11-jdk-slim
 ---> e0ec44868998
Step 2/6 : WORKDIR /app
 ---> Running in 2ff6c92192c5
Removing intermediate container 2ff6c92192c5
 ---> 067b8b2e6ea5
Step 3/6 : COPY . .
 ---> d67e314cf39d
Step 4/6 : RUN ./gradlew build -x test --no-daemon
 ---> Running in 921edf0dd584
Downloading https://services.gradle.org/distributions/gradle-5.0-all.zip
...........................................................................................................................

Welcome to Gradle 5.0!

Here are the highlights of this release:
 - Kotlin DSL 1.0
 - Task timeouts
 - Dependency alignment aka BOM support
 - Interactive `gradle init`

For more details see https://docs.gradle.org/5.0/release-notes.html

To honour the JVM settings for this build a new JVM will be forked. Please consider using the daemon: https://docs.gradle.org/5.0/userguide/gradle_daemon.html.
Daemon will be stopped at the end of the build stopping after processing

> Task :compileJava
> Task :processResources
> Task :classes
> Task :bootJar
> Task :jar SKIPPED
> Task :assemble
> Task :check
> Task :build

BUILD SUCCESSFUL in 1m 11s
3 actionable tasks: 3 executed
Removing intermediate container 921edf0dd584
 ---> 59e21aaacc9b
Step 5/6 : EXPOSE 8080
 ---> Running in df1e17458c66
Removing intermediate container df1e17458c66
 ---> 80a0d76c9bd0
Step 6/6 : CMD ["java", "-jar", "build/libs/spring-boot-micrometer-1.jar"]
 ---> Running in cb55d1c053cb
Removing intermediate container cb55d1c053cb
 ---> 6942e5ce4bee
Successfully built 6942e5ce4bee
Successfully tagged springboot-micrometer:latest
Building frontend
Step 1/9 : FROM node:9.11.1-alpine
9.11.1-alpine: Pulling from library/node
605ce1bd3f31: Pull complete
7cc38010b685: Pull complete
88a635599bc5: Pull complete
Digest: sha256:f8f6c69cce180a9a7c9fa685c86671b1e1f2ea7cc5f9a0dbe99d30cc7a0b6cbe
Status: Downloaded newer image for node:9.11.1-alpine
 ---> 9cc7800b3f3c
Step 2/9 : RUN npm install -g http-server
 ---> Running in b4f69bd66613
/usr/local/bin/http-server -> /usr/local/lib/node_modules/http-server/bin/http-server
/usr/local/bin/hs -> /usr/local/lib/node_modules/http-server/bin/http-server
+ http-server@0.11.1
added 25 packages in 2.324s
Removing intermediate container b4f69bd66613
 ---> ab07f7bab0d3
Step 3/9 : WORKDIR /app
 ---> Running in 3e3a07831f7b
Removing intermediate container 3e3a07831f7b
 ---> bea4607821b1
Step 4/9 : COPY package*.json ./
 ---> 3aff9df91db9
Step 5/9 : RUN npm install --only=production
 ---> Running in 09ac1b985ecd

> bootstrap-vue@2.0.0-rc.11 postinstall /app/node_modules/bootstrap-vue
> opencollective postinstall || exit 0

     *** Thank you for using bootstrap-vue! ***

Please consider donating to our open collective
     to help us maintain this package.

  https://opencollective.com/bootstrap-vue/donate

                    ***

added 60 packages in 5.857s
Removing intermediate container 09ac1b985ecd
 ---> cb05bc5a04c2
Step 6/9 : COPY . .
 ---> 3b15125379be
Step 7/9 : RUN npm run build
 ---> Running in 10830a6eb3bc

> frontend@0.1.0 build /app
> vue-cli-service build

sh: vue-cli-service: not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! frontend@0.1.0 build: `vue-cli-service build`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the frontend@0.1.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2019-01-07T13_32_20_966Z-debug.log
ERROR: Service 'frontend' failed to build: The command '/bin/sh -c npm run build' returned a non-zero code: 1
marhan commented 5 years ago

It seems to be an issue in npm.