Grunt watch throws a sync:dev not found error with Sails.js in Kubernetes










3















I use Minikube for simulating my Kubernetes production architecture.
In the cluster, I need to create a website and I decided to use Sails.js.



Here is my Kubernetes configuration :



apiVersion: v1
kind: PersistentVolume
metadata:
name: white-label-storage-persistent-volume
labels:
type: local
app: white-label
role: master
tier: backend
spec:
storageClassName: manual
capacity:
storage: 5Gi
accessModes:
- ReadWriteMany
hostPath:
path: "/white-label-data"
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: white-label-storage-persistent-volume-claim
labels:
app: white-label
role: master
tier: backend
spec:
storageClassName: manual
accessModes:
- ReadWriteMany
resources:
requests:
storage: 5Gi
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: white-label-deployment
labels:
app: white-label
role: master
tier: backend
spec:
replicas: 1
strategy:
type: RollingUpdate
selector:
matchLabels:
app: white-label
role: master
tier: backend
template:
metadata:
labels:
app: white-label
role: master
tier: backend
spec:
containers:
- name: white-label
image: pastel-white-label:v1
imagePullPolicy: IfNotPresent
workingDir: "/usr/src/app"
resources:
requests:
memory: 2Gi
cpu: 1
limits:
memory: 4Gi
cpu: 2
ports:
- containerPort: 1337
protocol: TCP
volumeMounts:
- mountPath: "/data"
name: white-label-persistent-volume
volumes:
- name: white-label-persistent-volume
persistentVolumeClaim:
claimName: white-label-storage-persistent-volume-claim
---
apiVersion: v1
kind: Service
metadata:
name: white-label-service
labels:
app: white-label
role: master
tier: backend
spec:
type: LoadBalancer
ports:
- port: 1337
protocol: TCP
nodePort: 30003
selector:
app: white-label
role: master
tier: backend
sessionAffinity: None
---
apiVersion: autoscaling/v1
kind: HorizontalPodAutoscaler
metadata:
name: white-label-hpa
labels:
app: white-label
role: master
tier: backend
namespace: default
spec:
maxReplicas: 5
minReplicas: 1
scaleTargetRef:
apiVersion: extensions/v1
kind: Deployment
name: white-label-deployment
targetCPUUtilizationPercentage: 80


And here is the pastel-white-label:v1 Docker image :



FROM node:10.13.0-stretch

WORKDIR /usr/src/app
COPY . ./

RUN npm install -g sails npm-check-updates
RUN npm install @sailshq/connect-redis --save
RUN npm install

CMD ["sails", "lift"]


When I start my cluster and build my pod, everything works like a charm.
My Sails.js log is spotless, I can see the home page in the browser: no problem at all. I use Sails.js v1.1.0 in Web app mode out of the box BTW. I can see as well that Grunt is launched and is watching.



Now if I edit a .less file though, I get an unfriendly:



debug: -------------------------------------------------------
error: ** Grunt :: An error occurred. **
error:
------------------------------------------------------------------------

Aborted due to warnings.
Running "watch" task
Waiting...
>> File "assets/styles/styleguide/colors.less" changed.
Loading "sync.js" tasks...ERROR
>> TypeError: Cannot read property 'length' of undefined
Warning: Task "sync:dev" not found.


I am sure my .less file has no error (hexa code edition), my .tmp folder is writable (touch .tmp/foo is working for instance) and I believe Grunt is correctly installed as it comes out of the box...



Then I really don't know what is going on here...



Do you guys have an idea, please ?



Thank you ahead










share|improve this question
























  • How do you know that your .tmp folder is writable in your pod? are you ssh-ing into your pod?

    – Rico
    Nov 13 '18 at 23:14











  • I ssh it indeed => kubectl exec -it white-label-deployment-- -- /bin/bash

    – Zaziffic
    Nov 14 '18 at 8:19















3















I use Minikube for simulating my Kubernetes production architecture.
In the cluster, I need to create a website and I decided to use Sails.js.



Here is my Kubernetes configuration :



apiVersion: v1
kind: PersistentVolume
metadata:
name: white-label-storage-persistent-volume
labels:
type: local
app: white-label
role: master
tier: backend
spec:
storageClassName: manual
capacity:
storage: 5Gi
accessModes:
- ReadWriteMany
hostPath:
path: "/white-label-data"
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: white-label-storage-persistent-volume-claim
labels:
app: white-label
role: master
tier: backend
spec:
storageClassName: manual
accessModes:
- ReadWriteMany
resources:
requests:
storage: 5Gi
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: white-label-deployment
labels:
app: white-label
role: master
tier: backend
spec:
replicas: 1
strategy:
type: RollingUpdate
selector:
matchLabels:
app: white-label
role: master
tier: backend
template:
metadata:
labels:
app: white-label
role: master
tier: backend
spec:
containers:
- name: white-label
image: pastel-white-label:v1
imagePullPolicy: IfNotPresent
workingDir: "/usr/src/app"
resources:
requests:
memory: 2Gi
cpu: 1
limits:
memory: 4Gi
cpu: 2
ports:
- containerPort: 1337
protocol: TCP
volumeMounts:
- mountPath: "/data"
name: white-label-persistent-volume
volumes:
- name: white-label-persistent-volume
persistentVolumeClaim:
claimName: white-label-storage-persistent-volume-claim
---
apiVersion: v1
kind: Service
metadata:
name: white-label-service
labels:
app: white-label
role: master
tier: backend
spec:
type: LoadBalancer
ports:
- port: 1337
protocol: TCP
nodePort: 30003
selector:
app: white-label
role: master
tier: backend
sessionAffinity: None
---
apiVersion: autoscaling/v1
kind: HorizontalPodAutoscaler
metadata:
name: white-label-hpa
labels:
app: white-label
role: master
tier: backend
namespace: default
spec:
maxReplicas: 5
minReplicas: 1
scaleTargetRef:
apiVersion: extensions/v1
kind: Deployment
name: white-label-deployment
targetCPUUtilizationPercentage: 80


And here is the pastel-white-label:v1 Docker image :



FROM node:10.13.0-stretch

WORKDIR /usr/src/app
COPY . ./

RUN npm install -g sails npm-check-updates
RUN npm install @sailshq/connect-redis --save
RUN npm install

CMD ["sails", "lift"]


When I start my cluster and build my pod, everything works like a charm.
My Sails.js log is spotless, I can see the home page in the browser: no problem at all. I use Sails.js v1.1.0 in Web app mode out of the box BTW. I can see as well that Grunt is launched and is watching.



Now if I edit a .less file though, I get an unfriendly:



debug: -------------------------------------------------------
error: ** Grunt :: An error occurred. **
error:
------------------------------------------------------------------------

Aborted due to warnings.
Running "watch" task
Waiting...
>> File "assets/styles/styleguide/colors.less" changed.
Loading "sync.js" tasks...ERROR
>> TypeError: Cannot read property 'length' of undefined
Warning: Task "sync:dev" not found.


I am sure my .less file has no error (hexa code edition), my .tmp folder is writable (touch .tmp/foo is working for instance) and I believe Grunt is correctly installed as it comes out of the box...



Then I really don't know what is going on here...



Do you guys have an idea, please ?



Thank you ahead










share|improve this question
























  • How do you know that your .tmp folder is writable in your pod? are you ssh-ing into your pod?

    – Rico
    Nov 13 '18 at 23:14











  • I ssh it indeed => kubectl exec -it white-label-deployment-- -- /bin/bash

    – Zaziffic
    Nov 14 '18 at 8:19













3












3








3








I use Minikube for simulating my Kubernetes production architecture.
In the cluster, I need to create a website and I decided to use Sails.js.



Here is my Kubernetes configuration :



apiVersion: v1
kind: PersistentVolume
metadata:
name: white-label-storage-persistent-volume
labels:
type: local
app: white-label
role: master
tier: backend
spec:
storageClassName: manual
capacity:
storage: 5Gi
accessModes:
- ReadWriteMany
hostPath:
path: "/white-label-data"
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: white-label-storage-persistent-volume-claim
labels:
app: white-label
role: master
tier: backend
spec:
storageClassName: manual
accessModes:
- ReadWriteMany
resources:
requests:
storage: 5Gi
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: white-label-deployment
labels:
app: white-label
role: master
tier: backend
spec:
replicas: 1
strategy:
type: RollingUpdate
selector:
matchLabels:
app: white-label
role: master
tier: backend
template:
metadata:
labels:
app: white-label
role: master
tier: backend
spec:
containers:
- name: white-label
image: pastel-white-label:v1
imagePullPolicy: IfNotPresent
workingDir: "/usr/src/app"
resources:
requests:
memory: 2Gi
cpu: 1
limits:
memory: 4Gi
cpu: 2
ports:
- containerPort: 1337
protocol: TCP
volumeMounts:
- mountPath: "/data"
name: white-label-persistent-volume
volumes:
- name: white-label-persistent-volume
persistentVolumeClaim:
claimName: white-label-storage-persistent-volume-claim
---
apiVersion: v1
kind: Service
metadata:
name: white-label-service
labels:
app: white-label
role: master
tier: backend
spec:
type: LoadBalancer
ports:
- port: 1337
protocol: TCP
nodePort: 30003
selector:
app: white-label
role: master
tier: backend
sessionAffinity: None
---
apiVersion: autoscaling/v1
kind: HorizontalPodAutoscaler
metadata:
name: white-label-hpa
labels:
app: white-label
role: master
tier: backend
namespace: default
spec:
maxReplicas: 5
minReplicas: 1
scaleTargetRef:
apiVersion: extensions/v1
kind: Deployment
name: white-label-deployment
targetCPUUtilizationPercentage: 80


And here is the pastel-white-label:v1 Docker image :



FROM node:10.13.0-stretch

WORKDIR /usr/src/app
COPY . ./

RUN npm install -g sails npm-check-updates
RUN npm install @sailshq/connect-redis --save
RUN npm install

CMD ["sails", "lift"]


When I start my cluster and build my pod, everything works like a charm.
My Sails.js log is spotless, I can see the home page in the browser: no problem at all. I use Sails.js v1.1.0 in Web app mode out of the box BTW. I can see as well that Grunt is launched and is watching.



Now if I edit a .less file though, I get an unfriendly:



debug: -------------------------------------------------------
error: ** Grunt :: An error occurred. **
error:
------------------------------------------------------------------------

Aborted due to warnings.
Running "watch" task
Waiting...
>> File "assets/styles/styleguide/colors.less" changed.
Loading "sync.js" tasks...ERROR
>> TypeError: Cannot read property 'length' of undefined
Warning: Task "sync:dev" not found.


I am sure my .less file has no error (hexa code edition), my .tmp folder is writable (touch .tmp/foo is working for instance) and I believe Grunt is correctly installed as it comes out of the box...



Then I really don't know what is going on here...



Do you guys have an idea, please ?



Thank you ahead










share|improve this question
















I use Minikube for simulating my Kubernetes production architecture.
In the cluster, I need to create a website and I decided to use Sails.js.



Here is my Kubernetes configuration :



apiVersion: v1
kind: PersistentVolume
metadata:
name: white-label-storage-persistent-volume
labels:
type: local
app: white-label
role: master
tier: backend
spec:
storageClassName: manual
capacity:
storage: 5Gi
accessModes:
- ReadWriteMany
hostPath:
path: "/white-label-data"
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: white-label-storage-persistent-volume-claim
labels:
app: white-label
role: master
tier: backend
spec:
storageClassName: manual
accessModes:
- ReadWriteMany
resources:
requests:
storage: 5Gi
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: white-label-deployment
labels:
app: white-label
role: master
tier: backend
spec:
replicas: 1
strategy:
type: RollingUpdate
selector:
matchLabels:
app: white-label
role: master
tier: backend
template:
metadata:
labels:
app: white-label
role: master
tier: backend
spec:
containers:
- name: white-label
image: pastel-white-label:v1
imagePullPolicy: IfNotPresent
workingDir: "/usr/src/app"
resources:
requests:
memory: 2Gi
cpu: 1
limits:
memory: 4Gi
cpu: 2
ports:
- containerPort: 1337
protocol: TCP
volumeMounts:
- mountPath: "/data"
name: white-label-persistent-volume
volumes:
- name: white-label-persistent-volume
persistentVolumeClaim:
claimName: white-label-storage-persistent-volume-claim
---
apiVersion: v1
kind: Service
metadata:
name: white-label-service
labels:
app: white-label
role: master
tier: backend
spec:
type: LoadBalancer
ports:
- port: 1337
protocol: TCP
nodePort: 30003
selector:
app: white-label
role: master
tier: backend
sessionAffinity: None
---
apiVersion: autoscaling/v1
kind: HorizontalPodAutoscaler
metadata:
name: white-label-hpa
labels:
app: white-label
role: master
tier: backend
namespace: default
spec:
maxReplicas: 5
minReplicas: 1
scaleTargetRef:
apiVersion: extensions/v1
kind: Deployment
name: white-label-deployment
targetCPUUtilizationPercentage: 80


And here is the pastel-white-label:v1 Docker image :



FROM node:10.13.0-stretch

WORKDIR /usr/src/app
COPY . ./

RUN npm install -g sails npm-check-updates
RUN npm install @sailshq/connect-redis --save
RUN npm install

CMD ["sails", "lift"]


When I start my cluster and build my pod, everything works like a charm.
My Sails.js log is spotless, I can see the home page in the browser: no problem at all. I use Sails.js v1.1.0 in Web app mode out of the box BTW. I can see as well that Grunt is launched and is watching.



Now if I edit a .less file though, I get an unfriendly:



debug: -------------------------------------------------------
error: ** Grunt :: An error occurred. **
error:
------------------------------------------------------------------------

Aborted due to warnings.
Running "watch" task
Waiting...
>> File "assets/styles/styleguide/colors.less" changed.
Loading "sync.js" tasks...ERROR
>> TypeError: Cannot read property 'length' of undefined
Warning: Task "sync:dev" not found.


I am sure my .less file has no error (hexa code edition), my .tmp folder is writable (touch .tmp/foo is working for instance) and I believe Grunt is correctly installed as it comes out of the box...



Then I really don't know what is going on here...



Do you guys have an idea, please ?



Thank you ahead







kubernetes gruntjs sails.js minikube






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 13 '18 at 23:09









Rico

27.2k94865




27.2k94865










asked Nov 13 '18 at 22:32









ZazifficZaziffic

19618




19618












  • How do you know that your .tmp folder is writable in your pod? are you ssh-ing into your pod?

    – Rico
    Nov 13 '18 at 23:14











  • I ssh it indeed => kubectl exec -it white-label-deployment-- -- /bin/bash

    – Zaziffic
    Nov 14 '18 at 8:19

















  • How do you know that your .tmp folder is writable in your pod? are you ssh-ing into your pod?

    – Rico
    Nov 13 '18 at 23:14











  • I ssh it indeed => kubectl exec -it white-label-deployment-- -- /bin/bash

    – Zaziffic
    Nov 14 '18 at 8:19
















How do you know that your .tmp folder is writable in your pod? are you ssh-ing into your pod?

– Rico
Nov 13 '18 at 23:14





How do you know that your .tmp folder is writable in your pod? are you ssh-ing into your pod?

– Rico
Nov 13 '18 at 23:14













I ssh it indeed => kubectl exec -it white-label-deployment-- -- /bin/bash

– Zaziffic
Nov 14 '18 at 8:19





I ssh it indeed => kubectl exec -it white-label-deployment-- -- /bin/bash

– Zaziffic
Nov 14 '18 at 8:19












1 Answer
1






active

oldest

votes


















1














I think you are running into exactly this. Looks like it's specific to the node version. You can try an earlier version for your node docker image:



FROM node:8.12.0-stretch





share|improve this answer























  • I saw that post but did not try. I do that straight away and I let you know. It is the only post I found regarding sync:dev issue so I do hope that'll do the trick !

    – Zaziffic
    Nov 14 '18 at 8:21











  • And it did the trick! By rolling back the node version to 8.12, it is now back on track and Grunt is a happy bunny! The problem though is that 8.12 is not the LTS version of Node anymore so I just exposed my website... But it'll do for now. It is strange it worked though as my package.json shows : "engines": "node": ">=10.13"

    – Zaziffic
    Nov 14 '18 at 8:48












  • BTW, I tried "FROM node:latest" and I still had the issue so it is a Node 10+ problem I guess.

    – Zaziffic
    Nov 14 '18 at 8:51











  • Yes, latest still has the problem. I added a comment on the issue. Can you accept the answer if it's good?

    – Rico
    Nov 14 '18 at 15:35











  • Thanks for posting this, I'm getting this same issue.

    – Noitidart
    Nov 28 '18 at 12:51










Your Answer






StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53290515%2fgrunt-watch-throws-a-syncdev-not-found-error-with-sails-js-in-kubernetes%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









1














I think you are running into exactly this. Looks like it's specific to the node version. You can try an earlier version for your node docker image:



FROM node:8.12.0-stretch





share|improve this answer























  • I saw that post but did not try. I do that straight away and I let you know. It is the only post I found regarding sync:dev issue so I do hope that'll do the trick !

    – Zaziffic
    Nov 14 '18 at 8:21











  • And it did the trick! By rolling back the node version to 8.12, it is now back on track and Grunt is a happy bunny! The problem though is that 8.12 is not the LTS version of Node anymore so I just exposed my website... But it'll do for now. It is strange it worked though as my package.json shows : "engines": "node": ">=10.13"

    – Zaziffic
    Nov 14 '18 at 8:48












  • BTW, I tried "FROM node:latest" and I still had the issue so it is a Node 10+ problem I guess.

    – Zaziffic
    Nov 14 '18 at 8:51











  • Yes, latest still has the problem. I added a comment on the issue. Can you accept the answer if it's good?

    – Rico
    Nov 14 '18 at 15:35











  • Thanks for posting this, I'm getting this same issue.

    – Noitidart
    Nov 28 '18 at 12:51















1














I think you are running into exactly this. Looks like it's specific to the node version. You can try an earlier version for your node docker image:



FROM node:8.12.0-stretch





share|improve this answer























  • I saw that post but did not try. I do that straight away and I let you know. It is the only post I found regarding sync:dev issue so I do hope that'll do the trick !

    – Zaziffic
    Nov 14 '18 at 8:21











  • And it did the trick! By rolling back the node version to 8.12, it is now back on track and Grunt is a happy bunny! The problem though is that 8.12 is not the LTS version of Node anymore so I just exposed my website... But it'll do for now. It is strange it worked though as my package.json shows : "engines": "node": ">=10.13"

    – Zaziffic
    Nov 14 '18 at 8:48












  • BTW, I tried "FROM node:latest" and I still had the issue so it is a Node 10+ problem I guess.

    – Zaziffic
    Nov 14 '18 at 8:51











  • Yes, latest still has the problem. I added a comment on the issue. Can you accept the answer if it's good?

    – Rico
    Nov 14 '18 at 15:35











  • Thanks for posting this, I'm getting this same issue.

    – Noitidart
    Nov 28 '18 at 12:51













1












1








1







I think you are running into exactly this. Looks like it's specific to the node version. You can try an earlier version for your node docker image:



FROM node:8.12.0-stretch





share|improve this answer













I think you are running into exactly this. Looks like it's specific to the node version. You can try an earlier version for your node docker image:



FROM node:8.12.0-stretch






share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 14 '18 at 0:22









RicoRico

27.2k94865




27.2k94865












  • I saw that post but did not try. I do that straight away and I let you know. It is the only post I found regarding sync:dev issue so I do hope that'll do the trick !

    – Zaziffic
    Nov 14 '18 at 8:21











  • And it did the trick! By rolling back the node version to 8.12, it is now back on track and Grunt is a happy bunny! The problem though is that 8.12 is not the LTS version of Node anymore so I just exposed my website... But it'll do for now. It is strange it worked though as my package.json shows : "engines": "node": ">=10.13"

    – Zaziffic
    Nov 14 '18 at 8:48












  • BTW, I tried "FROM node:latest" and I still had the issue so it is a Node 10+ problem I guess.

    – Zaziffic
    Nov 14 '18 at 8:51











  • Yes, latest still has the problem. I added a comment on the issue. Can you accept the answer if it's good?

    – Rico
    Nov 14 '18 at 15:35











  • Thanks for posting this, I'm getting this same issue.

    – Noitidart
    Nov 28 '18 at 12:51

















  • I saw that post but did not try. I do that straight away and I let you know. It is the only post I found regarding sync:dev issue so I do hope that'll do the trick !

    – Zaziffic
    Nov 14 '18 at 8:21











  • And it did the trick! By rolling back the node version to 8.12, it is now back on track and Grunt is a happy bunny! The problem though is that 8.12 is not the LTS version of Node anymore so I just exposed my website... But it'll do for now. It is strange it worked though as my package.json shows : "engines": "node": ">=10.13"

    – Zaziffic
    Nov 14 '18 at 8:48












  • BTW, I tried "FROM node:latest" and I still had the issue so it is a Node 10+ problem I guess.

    – Zaziffic
    Nov 14 '18 at 8:51











  • Yes, latest still has the problem. I added a comment on the issue. Can you accept the answer if it's good?

    – Rico
    Nov 14 '18 at 15:35











  • Thanks for posting this, I'm getting this same issue.

    – Noitidart
    Nov 28 '18 at 12:51
















I saw that post but did not try. I do that straight away and I let you know. It is the only post I found regarding sync:dev issue so I do hope that'll do the trick !

– Zaziffic
Nov 14 '18 at 8:21





I saw that post but did not try. I do that straight away and I let you know. It is the only post I found regarding sync:dev issue so I do hope that'll do the trick !

– Zaziffic
Nov 14 '18 at 8:21













And it did the trick! By rolling back the node version to 8.12, it is now back on track and Grunt is a happy bunny! The problem though is that 8.12 is not the LTS version of Node anymore so I just exposed my website... But it'll do for now. It is strange it worked though as my package.json shows : "engines": "node": ">=10.13"

– Zaziffic
Nov 14 '18 at 8:48






And it did the trick! By rolling back the node version to 8.12, it is now back on track and Grunt is a happy bunny! The problem though is that 8.12 is not the LTS version of Node anymore so I just exposed my website... But it'll do for now. It is strange it worked though as my package.json shows : "engines": "node": ">=10.13"

– Zaziffic
Nov 14 '18 at 8:48














BTW, I tried "FROM node:latest" and I still had the issue so it is a Node 10+ problem I guess.

– Zaziffic
Nov 14 '18 at 8:51





BTW, I tried "FROM node:latest" and I still had the issue so it is a Node 10+ problem I guess.

– Zaziffic
Nov 14 '18 at 8:51













Yes, latest still has the problem. I added a comment on the issue. Can you accept the answer if it's good?

– Rico
Nov 14 '18 at 15:35





Yes, latest still has the problem. I added a comment on the issue. Can you accept the answer if it's good?

– Rico
Nov 14 '18 at 15:35













Thanks for posting this, I'm getting this same issue.

– Noitidart
Nov 28 '18 at 12:51





Thanks for posting this, I'm getting this same issue.

– Noitidart
Nov 28 '18 at 12:51

















draft saved

draft discarded
















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53290515%2fgrunt-watch-throws-a-syncdev-not-found-error-with-sails-js-in-kubernetes%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Top Tejano songwriter Luis Silva dead of heart attack at 64

政党

天津地下鉄3号線