[QUESTION] dockerfile command may need run yarn start not yarn build-and-start?

[lee88688]

Question

in Dockerfile, this has run yarn build

dashy/Dockerfile

Line 25 in 382f8f3

RUN yarn build --mode production

why is there need another build in start command in yarn build-and-start

dashy/Dockerfile

Line 45 in 382f8f3

CMD [ "yarn", "build-and-start" ]

I override command using yarn start which works too, so there is some feature I discover?

Category

Setup and Deployment

Please tick the boxes

• You are using a supported version of Dashy (check the first two digits of the version number)
• You've checked that this question hasn't already been raised
• You've checked the docs and troubleshooting guide
• You agree to the code of conduct

[Lissy93]

I think you're right @lee88688 - thanks for the suggestion.
I'll do a bit more testing, but if all that passes, this will be released later this week, in 3.0.1.

[Lissy93]

Yup, you were right. Much better without the second build!
Merged 1bbb91b into #1542 and released to 3.0.1

[CrazyWolf13]

Hi @lee88688

I temporarly had to revert the changes, as issues like this #1559 would arise, as the container is not watching for changes on the files.

Until lissy has time to properly look into this, we will keep this change reverted.

But if you don't repull the :latest tag, that should not change anything for you.

[girlpunk]

This is still outstanding, and causes the container to fail to start when run as a non-root user (which it always should be for security purposes)

[CrazyWolf13]

@girlpunk Looking at the current state of this project, I don't think this will get fixed soon as well as many other big problems.

I've made the hard decision to switch to something else like homepage or homarr, for better stability and even much better security.