We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It seems as recent Docker version requires us to change the way we build our images. I get this message, across both macOS and Linux:
I confirmed this did not happen (in our repo) on Docker < 26.0.0.
Here's a similar problem someone else is facing: https://stackoverflow.com/questions/66680559/docker-unable-to-copy-git-folder.
The proper way to solve this could be saving the Hajk version number and most recent commit hash into a file, rather than parsing it on-the-flight, as we currently do in https://github.com/hajkmap/Hajk/blob/49f36f5099cc8914c2947c1eb21e6f3011d35de0/apps/client/prebuild.js.
But that's for the Docker build. Ideally, we must find a solution that works for usual npm run build too. Ideas @hajkmap/dev?
npm run build
The text was updated successfully, but these errors were encountered:
Looks like it can be solved by properly pointing to the directory (using trailing slash).
Sorry, something went wrong.
e0d0e9f
jacobwod
No branches or pull requests
It seems as recent Docker version requires us to change the way we build our images. I get this message, across both macOS and Linux:
I confirmed this did not happen (in our repo) on Docker < 26.0.0.
Here's a similar problem someone else is facing: https://stackoverflow.com/questions/66680559/docker-unable-to-copy-git-folder.
The proper way to solve this could be saving the Hajk version number and most recent commit hash into a file, rather than parsing it on-the-flight, as we currently do in https://github.com/hajkmap/Hajk/blob/49f36f5099cc8914c2947c1eb21e6f3011d35de0/apps/client/prebuild.js.
But that's for the Docker build. Ideally, we must find a solution that works for usual
npm run build
too. Ideas @hajkmap/dev?The text was updated successfully, but these errors were encountered: