dosubot[bot] commented on issue #29583:
URL: https://github.com/apache/superset/issues/29583#issuecomment-2226836762
<!-- Greeting -->
Hey there, @F041! 👋 I'm here to help you with any bugs, questions, or
contributions you have regarding the repository.
<!-- Answer -->
To resolve the error related to the `docker/.env` file being an invalid type
when running `docker-compose up` for Apache Superset on an Ubuntu ARM machine,
ensure that the `.env` file is correctly formatted and does not contain any
syntax errors or unsupported characters. The provided `.env` file content
appears to be correctly formatted. Here is the content for reference:
```env
COMPOSE_PROJECT_NAME=superset
# database configurations (do not modify)
DATABASE_DB=superset
DATABASE_HOST=db
# Make sure you set this to a unique secure random value on production
DATABASE_PASSWORD=superset
DATABASE_USER=superset
EXAMPLES_DB=examples
EXAMPLES_HOST=db
EXAMPLES_USER=examples
# Make sure you set this to a unique secure random value on production
EXAMPLES_PASSWORD=examples
EXAMPLES_PORT=5432
# database engine specific environment variables
# change the below if you prefer another database engine
DATABASE_PORT=5432
DATABASE_DIALECT=postgresql
POSTGRES_DB=superset
POSTGRES_USER=superset
# Make sure you set this to a unique secure random value on production
POSTGRES_PASSWORD=superset
#MYSQL_DATABASE=superset
#MYSQL_USER=superset
#MYSQL_PASSWORD=superset
#MYSQL_RANDOM_ROOT_PASSWORD=yes
# Add the mapped in /app/pythonpath_docker which allows devs to override
stuff
PYTHONPATH=/app/pythonpath:/app/docker/pythonpath_dev
REDIS_HOST=redis
REDIS_PORT=6379
FLASK_DEBUG=true
SUPERSET_ENV=development
SUPERSET_LOAD_EXAMPLES=yes
CYPRESS_CONFIG=false
SUPERSET_PORT=8088
MAPBOX_API_KEY=''
# Make sure you set this to a unique secure random value on production
SUPERSET_SECRET_KEY=TEST_NON_DEV_SECRET
ENABLE_PLAYWRIGHT=false
PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true
BUILD_SUPERSET_FRONTEND_IN_DOCKER=true
```
Ensure that the file is saved with the correct `.env` extension and does not
contain any hidden characters or formatting issues that might cause Docker to
misinterpret it. If the issue persists, try the following steps:
1. **Check for Hidden Characters**: Ensure there are no hidden characters or
BOM (Byte Order Mark) at the beginning of the file. You can use a text editor
like `vim` or `nano` to check and remove any hidden characters.
2. **File Encoding**: Ensure the file is saved with UTF-8 encoding without
BOM.
3. **Line Endings**: Ensure the file uses Unix-style line endings (`\n`).
You can convert the line endings using a tool like `dos2unix`:
```sh
dos2unix docker/.env
```
4. **Permissions**: Ensure the file has the correct permissions to be read
by Docker:
```sh
chmod 644 docker/.env
```
After verifying and correcting these potential issues, try running
`docker-compose up` again
<sup>[[1]](https://github.com/apache/superset/blob/master/docker/.env)</sup>.
<!-- Dosu Comment Footer -->
*To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
