We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When doing the self host setup, I get the following log error when docker logs -f
docker logs -f
hbp-dev-minio | mkdir: can't create directory '/data/nhost': Permission denied
I'm usingdocker-compose.yml` as the example:
I'm using
version: "3.6" services: postgres: image: "nhost/postgres:12-v0.0.6" restart: always volumes: - "./db_data:/var/lib/postgresql/data" environment: POSTGRES_PASSWORD: pgpassword POSTGRES_DB: postgres graphql-engine: image: "hasura/graphql-engine:v2.0.1" depends_on: - postgres restart: always ports: - "8080:8080" environment: HASURA_GRAPHQL_DATABASE_URL: >- postgres://postgres:pgpassword@postgres:5432/postgres HASURA_GRAPHQL_ENABLE_CONSOLE: "true" HASURA_GRAPHQL_ADMIN_SECRET: hello123 HASURA_GRAPHQL_JWT_SECRET: >- {"type":"HS256", "key": "jhyu89jiuhyg7678hoijhuytf7ghjiasodibagsdga9dha8os7df97a6sdgh9asudgo7f7g8h1uuoyafsod8pgasipdg8aps9dhaiaisydg8agsd87gasd9oihasd87gas78d"} HASURA_GRAPHQL_UNAUTHORIZED_ROLE: public command: - graphql-engine - serve hasura-backend-plus: image: "nhost/hasura-backend-plus:latest" container_name: hbp-dev-hbp depends_on: - graphql-engine restart: always ports: - "4000:4000" environment: HOST: 0.0.0.0 PORT: 4000 DATABASE_URL: >- postgres://postgres:pgpassword@postgres:5432/postgres SERVER_URL: "http://localhost:4000" HASURA_ENDPOINT: "http://graphql-engine:8080/v1/graphql" HASURA_GRAPHQL_ADMIN_SECRET: hello123 JWT_KEY: >- jhyu89jiuhyg7678hoijhuytf7ghjiasodibagsdga9dha8os7df97a6sdgh9asudgo7f7g8h1uuoyafsod8pgasipdg8aps9dhai;sd JWT_ALGORITHM: HS256 ALLOWED_REDIRECT_URLS: "http://localhost" JWT_CUSTOM_FIELDS: "" S3_ENDPOINT: "minio:9000" S3_SSL_ENABLED: "false" S3_BUCKET: nhost S3_ACCESS_KEY_ID: 5a7bdb5f42c41e0622bf61d6e08d5537 S3_SECRET_ACCESS_KEY: 9e1c40c65a615a5b52f52aeeaf549944ec53acb1dff4a0bf01fb58e969f915c8 AUTO_ACTIVATE_NEW_USERS: "true" PROVIDER_SUCCESS_REDIRECT: "http://localhost:3001/success" PROVIDER_FAILURE_REDIRECT: "http://localhost:3001/failed" HIBP_ENABLED: "false" DEFAULT_ALLOWED_USER_ROLES: "user,me" ALLOWED_USER_ROLES: "user,me" REGISTRATION_CUSTOM_FIELDS: "display_name" COOKIE_SECURE: "false" COOKIE_SECRET: "somelongvalue" REDIRECT_URL_SUCCESS: "http://localhost:3000" REDIRECT_URL_ERROR: "http://localhost:3000/fail" minio: image: "minio/minio:RELEASE.2020-06-18T02-23-35Z" container_name: hbp-dev-minio user: "999:1001" restart: always environment: MINIO_ACCESS_KEY: 5a7bdb5f42c41e0622bf61d6e08d5537 MINIO_SECRET_KEY: 9e1c40c65a615a5b52f52aeeaf549944ec53acb1dff4a0bf01fb58e969f915c8 entrypoint: sh command: -c 'mkdir -p /data/nhost && /usr/bin/minio server /data' ports: - "9000:9000" volumes: - "./minio_data:/data"
It is expected that minio up and running
Maybe related that I'm not the 1000:1000 user.
The text was updated successfully, but these errors were encountered:
Could you try to remove the user: "999:1001" and see what happens?
user: "999:1001"
I've only tried this docker-compose file on Mac thus far.
Sorry, something went wrong.
Thank you @elitan. It did allowed the creation of minio's setup folders.
Nice. So did you get everything working?
No branches or pull requests
When doing the self host setup, I get the following log error when
docker logs -f
I'm using
docker-compose.yml` as the example:It is expected that minio up and running
Maybe related that I'm not the 1000:1000 user.
The text was updated successfully, but these errors were encountered: