Bug: Build Config - Docker file path gets preferred over custom docker file

[yuvii]

📜 Description

If there's a dockerfile path configured in the build stage, if you switch to "Create Dockerfile" option the deployment would still try to build from the file path provided.

👟 Reproduction steps

Create an app, in the build configuration enter a path for a Dockerfile, then switch to "Create Dockerfile". The deployment would then look for the file specified in the path, ignoring the created dockerfile.

👍 Expected behavior

The deployment should use the selected dockerfile, regardless if there are other values available

👎 Actual Behavior

Devtron picks the docker image from the path if a value is provided, ignoring what is actively selected.

☸ Kubernetes version

EKS 1.30

Cloud provider

AWS

🌍 Browser

Opera

🧱 Your Environment

No response

✅ Proposed Solution

No response

👀 Have you spent some time to check if this issue has been raised before?

• [X] I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

• [X] I have read the Code of Conduct

[deepak-devtron]

Hi Yuval, The custom Dockerfile feature is working as expected. However, to run the docker build command, the content needs to be saved in a file. Currently, the path is being picked from the 'I have Dockerfile' tab, which may not provide the best user experience. We appreciate your feedback and will consider this improvement in an upcoming release.

[abhibhaw]

@yuvii are you experiencing the same as @deepak-devtron or something different?