You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note you always can adapt env variables for your deployment (e.g. using docker-compose.yaml).
If you want to contribute a solution with a different proposal, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.
Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.
I'm happy to do a PR removing HOME. I'm pretty sure it doesn't ever make sense to pre-emptively set it like this. I guess I'd assume somebody once had a reason for it.
Name and Version
bitnami/mysql
What architecture are you using?
arm64
What steps will reproduce the bug?
What is the expected behavior?
HOME
should be the home directory of the userWhat do you see instead?
HOME is always set to
/
, as a result of the ENV HOME=/ in https://github.com/bitnami/containers/blob/main/bitnami/mysql/8.0/debian-12/Dockerfile#L21-L24Additional information
DDEV's ddev-dbserver adds an extra layer to bitnami/mysql:8.0 with a user matching the host user. But it doesn't work right because $HOME is broken.
In added layer
ENV HOME=""
resolves this problem, but I don't think theENV HOME=/
is appropriate in any case.The text was updated successfully, but these errors were encountered: