1.30.5 permission problems #469
Replies: 14 comments
-
I'm facing the same issue. @mathias4github , kindly asking when do I have to execute the script? The container does not start up when executing the stuff within Thanks! |
Beta Was this translation helpful? Give feedback.
-
Sorry guys, this is an upshot of letting the server run as a delegated user. If you add:
Or whatever UID your files in the var folder are owned by To your environment variables, that will set the user to www-data:www-data. I guess you are mounting file system folders, not docker volumes. Is that right? |
Beta Was this translation helpful? Give feedback.
-
@tobybatch it depends. Typically, I mount volumes: volumes: |
Beta Was this translation helpful? Give feedback.
-
tried it with the following options in the docker compose file: user: 33:33 neither of them fixed the bug |
Beta Was this translation helpful? Give feedback.
-
I don't mount any volume or folder. Here is my docker-compose.yml. Currently I'm working on the topic to get rid of the separate IPv4 Maybe I have an additional
|
Beta Was this translation helpful? Give feedback.
-
OK, I've rolled back that work, pushed, and re-run the builds. Pull fresh 1.30.5 and try again. The ownership may need to be fixed by hand. Sorry. I'll have another go at this later with a better view on what it will mean for existing installs. Thanks, and Sorry |
Beta Was this translation helpful? Give feedback.
-
I have the same problem with the latest build of the container (1h ago). Here are the
Here are the rights in the
How can I correct the ownership in my docker-compose file ? |
Beta Was this translation helpful? Give feedback.
-
As Toby mentioned: He reverted the change. Take care that you are using the latest image. I'm fine with the rollback. |
Beta Was this translation helpful? Give feedback.
-
I still have the same problem with the |
Beta Was this translation helpful? Give feedback.
-
I had the same issue. For the application container, I only have the following volumes: volumes:
- /data/kimai/config/local.yaml:/opt/kimai/config/packages/local.yaml:ro` To fix it, I:
The new container has the correct permissions, and everything is working as expected. Just make sure you don't remove your database container. |
Beta Was this translation helpful? Give feedback.
-
Still not working :/
I removed the image but the problem remains... |
Beta Was this translation helpful? Give feedback.
-
1.30.5 is the version that was republished. |
Beta Was this translation helpful? Give feedback.
-
Sorry, but I stopped and removed all containers, used The
From the console inside the container, I cannot chown the folder, since I don't have the permissions :/ What can I do to restore the rights of that folder ? |
Beta Was this translation helpful? Give feedback.
-
I read the docs and solved it ^^
|
Beta Was this translation helpful? Give feedback.
-
container comes up but serves a 500 error.
if you add the script:
`#!/bin/bash
if [[ ! -d "var/" || ! -d "var/cache/prod/" ]];
then
echo "Cache directory does not exist at: var/cache/prod/"
exit 1
fi
if [[ ! -f "bin/console" ]];
then
echo "Kimai console does not exist at: bin/console"
exit 1
fi
rm -r var/cache/prod/*
bin/console kimai:reload --env=prod
chown -R www-kimai .
chgrp -R www-data .
chmod -R g+r .
chmod -R 775 var/`
it comes up and works ... until you reboot the container
Beta Was this translation helpful? Give feedback.
All reactions