-
Notifications
You must be signed in to change notification settings - Fork 398
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
Deployment is not halted if there is no Dockerfile #237
Comments
Ah, I see that there's already a ticket for this. Probably, it makes sense to close this one. |
Jberczel
added a commit
to Jberczel/mrsk
that referenced
this issue
May 1, 2023
Add checks for: * Docker installed locally * Docker buildx plugin installed locally (not currently required for native/local build) * Dockerfile exists Checks will halt deployment and provide more specific error messages. Also adds a cli subcommand: `mrsk build dependencies` Fixes: basecamp#109 and basecamp#237
Jberczel
added a commit
to Jberczel/mrsk
that referenced
this issue
May 1, 2023
Add checks for: * Docker installed locally * Docker buildx plugin installed locally * Dockerfile exists If checks fail, it will halt deployment and provide more specific error messages. Also adds a cli subcommand: `mrsk build dependencies` Fixes: basecamp#109 and basecamp#237
Fixed via #256. |
Now it requires a Dockerfile even when there should be none, i.e. when I am deploying some public image from Docker Hub. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi team,
mrsk doesn't check whether Dockerfile exists or not.
In my project, Dockerfile is located not in the root folder and I have forgotten to tell it to mrsk.
However, non-existent Dockerfile didn't stop mrsk to attempt deployment. Ofc, it failed, but the reason was not an easy one to find. I suspect that output will look like the same if one makes a typo in config for the Dockerfile path variable.
The text was updated successfully, but these errors were encountered: