Open byronwall opened 5 months ago
My Coolify instance bumped to beta 277 but still experiences the same problems. I did not expect a fix based on release notes but wanted to provide an update if that's any help.
Dumb question: are the ENV variables specified in the Coolify settings supposed to end up in a .env
file that eventually ends up in the Docker scope? That is, should this work the way I assume, or am I wrong? I read through a bit of the PHP code, and it seemed that Coolify is trying to write a .env
based on the settings, but I don't have a good way to debug it.
If I'm wrong about these ending up in a .env
, I can easily modify the compose file to call out the variables, but I was hoping to avoid that because I'm lazy.
As an aside, thanks for building and maintaining Coolify. It really is a powerful platform that lets me not worry about a bunch of these details that I know are no fun to get right.
So I got this working. I think the problem was me. Or at least my ignorance kept me from solving things when I first reported the issue.
I eventually read the error message closely and SSH'ed into the box to troubleshoot. Ultimately, .env
actually was a directory for some reason. I simply did rmdir .env
to knock it out and start over. That immediately allowed Coolify to progress and build containers.
I'm not sure how it got into that state. When I originally went looking for the .env
file, I forgot that ls
does not show dot files by default. I assume that no .env
was present. I should really stop forgetting how ls
works. After I eventually ran ls -a
, it became clear that something existed as .env
, but it was indeed a directory.
After things deployed again, I changed an ENV var in the Coolify configuration. After another deploy, I confirm that setting correctly ended up in the .env
file on disk, and the app reflects the change.
I guess my only comments at this point are:
.env
file that the container uses. Given that, the yellow text saying This variable is not found in the compose file, so it won't be used.
is downright confusing.Feel free to close this issue, unless you see anything actionable. I am good to go.
@byronwall I would suggest setting the Environment Variabels in the compose file and then in the UI much more practical then the file approach.
@byronwall I'm trying to deploy librechat on coolify as well. I see you have removed the client
container which is present in the original repo from [your docker compose file](https://github.com/byronwall/LibreChat/blob/main/deploy-compose.yml}.
I successfully deployed the containers of the project after forking it, except the client
one which is an nginx image and I'm getting port 443 already exposed
error. How did you manage to deploy the project, and how are you accessing the client if you've removed it from the docker compose file?
@saeedesmaili, I expose the api
service directly with a domain. I then access LibreChat via that link/url.
I think after some tinkering/reviewing, I convinced myself that the client
service was just a thin proxy in front of the api
service. Regardless, it does actually work with HTTPS.
Going down my list of settings, they go like:
Docker Compose
https:// ???
where ???
is under my main coolify instance - if you email me, I can be less vague... trying to avoid doxing my server if possible. I just clicked generate domain
for API
and took whatever it made./
/deploy-compose.yml
docker compose -f ./deploy-compose.yml up -d --pull always
-- I did this to ensure that it would actually download the :latest
tag on LibreChat containers. I could not get it to upgrade from 0.73 to 0.74 without this nudge.I also copied most of the available environment variables into the Coolify ENV section. Most of them are still at default values, but I like having them available in case I want to change anything.
I have the same problem
tee: /data/coolify/applications/mccso4oo0kk0gow8soo00ggs/.env: Permission denied
anyway to fix this?
Description
I am getting an error when trying to deploy an updated LibreChat. It fails with message below about
env being a directory
The application is already deployed and running OK, but I want to update it. Unfortunately, I cannot determine what is going wrong on the re-deploy.
Since I did not want to mess with a volume or .env file, I copied all of the expected settings to Coolify's ENV section.
Am I missing something obvious, or is there something odd going on with ENV variables?
A snippet of that section shown here:
Minimal Reproduction (if possible, example repository)
Repo: https://github.com/byronwall/LibreChat
Steps:
I am trying to deploy with the
deploy-compose.yml
file: https://github.com/byronwall/LibreChat/blob/main/deploy-compose.ymlException or Error
Relevant part:
Full log:
Version
4.0.0 beta 271