Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CONFIG_FILE is readonly, preventing the use of a custom config file #10

Closed
tperrindell opened this issue May 16, 2022 · 1 comment
Closed
Assignees

Comments

@tperrindell
Copy link

Hi,

I imported my existing config when I migrated from a standalone server installation to docker.

Yesterday's update broke my installation. At first I thought it was due to the UID, so I had to change my system for it to match the values of 1000/1000, but that didn't fix anything.

When reading the new commit for the entrypoint.sh, 6a9d8f5

The variable CONFIG_FILE is set as readonly.

Therefore, the code at lines 58ish can't work :

if [[ -f "$MUMBLE_CUSTOM_CONFIG_FILE" ]]; then
	echo "Using manually specified config file at $MUMBLE_CUSTOM_CONFIG_FILE"
	echo "All MUMBLE_CONFIG variables will be ignored"
	CONFIG_FILE="$MUMBLE_CUSTOM_CONFIG_FILE"
else

Because the variable is readonly...

Can you revert that commit or correct the problem please ?

@azlux azlux self-assigned this May 16, 2022
@azlux
Copy link
Collaborator

azlux commented May 16, 2022

Should be fixed now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants