Skip to content
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

Add possibility to have a custom named Dockerfile #1030

Open
lars-m-leadec opened this issue Nov 14, 2023 · 1 comment
Open

Add possibility to have a custom named Dockerfile #1030

lars-m-leadec opened this issue Nov 14, 2023 · 1 comment
Labels
enhancement A PR providing an enhancement to existing functionality.

Comments

@lars-m-leadec
Copy link

What feature do you want to see added?

We have a project setup that needs a seperate Dockerfile. We have a Dockerfile and a file called db.dockerfile.

With docker build there is a possibility to have a custom named Dockerfile "docker build -f customnamedDockerfile ."

See https://docs.docker.com/engine/reference/commandline/build/#file)

It would be nice to have that option in your plugin.

Upstream changes

No response

@lars-m-leadec lars-m-leadec added the enhancement A PR providing an enhancement to existing functionality. label Nov 14, 2023
@timtrense-leadec
Copy link

Indeed that would be useful.

Since the Dockerfile might be in a parent directory or subdirectory, it would be nice to be able to specify the full relative path for it.

Also, docker build can specify a "context" to build from (by default the current directory:

docker build -f db.dockerfile .

Indicated by the . Dot here)
When giving the possibility to the user to run docker build with non-default directory layouts, why not also add an option to specify the build context directory?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement A PR providing an enhancement to existing functionality.
Projects
None yet
Development

No branches or pull requests

2 participants