[Bug]: .env file not created for laravel with custom docker file which was working till yesterday

[margintopsolutions]

Error Message and Logs

fig: deploying failed with .env not present

but it is properly set in environment variables table

Steps to Reproduce

1.create a simple docker file for laravel deployment
2.set environment from coolify
3.run the docker file

Example Repository URL

No response

Coolify Version

v4.0.0-beta.440

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Ubuntu 24.04.3 LTS

Additional Information

No response

[coderabbitai]

A summary of the changes CodeRabbit can apply:

• Update app/Jobs/ApplicationDeploymentJob.php: change the condition at ~line 1231 to include 'dockerfile' and $this->application->dockerfile (so empty .env files are created for dockerfile-based deployments) and update accompanying comments to reflect Docker Compose, Docker Image, and Dockerfile cases.

• Modify app/Jobs/ApplicationDeploymentJob.php to clarify the comment and extend the empty .env creation logic so it applies not only to 'dockercompose' and 'dockerimage' but also to 'dockerfile' builds and when application->dockerfile is set (adjusted conditional and explanatory comment referencing the generated compose file).

• ✅ Create PR with these edits
• 📋 Get copyable edits

[djsisson]

There is no .env unless you now add one yourself, all env are in the environment which laravel will still pull from

However i believe php artisan key:generate does try to get the app key from the .env file
So either add an empty file from the dockerfile or in the repo, or just add the key as an env and remove the artisan command as its not then needed

[marvinvr]

I'm experiencing the same issue with a custom sveltekit / nodejs image. Problem is I can't build without having the env variables at build time. So what I did was copy the .env over, if I don't do that, I don't have the variables available either.

[roshankc123]

same issue with nixpack too -> UndefinedVar: Usage of undefined variable '$NIXPACKS_PATH' (line 18)

[roshankc123]

i was able to fix this by move all task that require env variables during build time to docker-entrypoint.sh , however now i need to change the docker file for all of my projects manually now.

[marcosinigaglia]

Using "Use Docker Build Secrets" solved the problem for me.

[cbratschi]

Probably related to #6731. Having issues with missing env variables during the build step too.

[WananiAdib]

Coolify used to create an .env file in the build context of Dockerfile yesterday and it stopped for us too!

I just hope these breaking changes would be mentioned in change logs or an easy way to rollback to previous coolify versions if an update changes.

[djsisson]

coolify no longer generates a .env during builds as under certain circumstances, it could end up in the final image, which would be 1) redundant (due to runtime injection) and 2) a potential security risk (path traversal)

instead coolify will now pass in build_args (or secrets if using) to docker for any env with is_buildtime ticked, there is no need to create or use a .env, as all frameworks will pull from environment first.

The fact that it worked prior without doing so was a bug, so if you are having issues, just make sure is_buildtime is ticked for any env required during build. Docker environments do not need a .env file.

[TomasKliner]

Could this be related to #7118 ?

[Cinzya]

Closing this in favor of #7118 as I strongly believe this is related. We can re-open if this doesn't get fixed when #7118 completes.