-
Notifications
You must be signed in to change notification settings - Fork 9
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
Error #166
Comments
The setup script randomly generates the secret key for MinIO, so I wonder if an invalid key is being generated. Can you please follow these steps to share the keys here safely? # Stop the server
docker compose down
# Back up the current MinIO secrets
mkdir -p backups && cp environment/minio.local.env backups/minio-backup.env
# Regenerate the secrets and invalidate the old ones
./scripts/setup-environment.sh
# Display the MinIO secret key
cat backups/minio-backup.env Then, please send the old secret key (the line starting with |
It looks like the key is fine, but the script output gives me another idea about what might be going wrong. By default, when you use Git in Windows to clone a repo, it converts the line endings in files from LF (Linux-style) to CRLF (Windows-style), which can break Bash scripts. This is why I recommend cloning the repo inside your WSL distro in the Tips for Windows Users section of the server setup guide. Can you try re-cloning the repo inside your WSL home directory? |
I did it using the ubuntu application, I didn't use GIT or WSL. |
Interesting. What's your Git version?
|
My git version is 2.43.0 |
What are the line endings of the scripts?
|
Which script? On the CMD? |
The script files in the repo - just run those two commands and send the output here. |
./setup.sh and docker compose up -d --build ? |
|
|
What should I do now? |
That is definitely the problem: half of your scripts have CRLF line endings, so those scripts won't work. That is also very strange - I have no idea why half of them would (apparently) randomly have different line endings. You should be able to rectify the issue by converting them all to LF line endings with the following commands.
|
What next? |
Re-run the setup script, it should be fixed if I'm right about the cause of the error. |
It makes the same error, (I run it with the Ubuntu app) |
Can you check if the scripts all have the correct line endings now? Run this and send the output here.
|
|
What should I do ? |
I am not sure what the problem is at this point, since fixing the line endings didn't solve it. |
Oh right, I wanted to try again with WSL but the problem is that I can't do the “cd” command if you don't mind, can you help me via Anydesk please? Thank you for your help |
I'm not sure what you mean here. The Ubuntu app is itself WSL: Ubuntu is a Linux distro that runs in the Windows Subsystem for Linux.
I'm sorry, but I don't have the time to provide 1-on-1 support for issues via remote desktop/video chat. |
Oh right, since I have two applications, one Ubuntu and one WSL |
Hello, I have an error when starting the script... Can you please help ?
The text was updated successfully, but these errors were encountered: