the s3-client service runs mc once right after the MinIO container starts. depends_on waits only for the container to start, not for MinIO to accept connections. If MinIO isn't ready, the bucket, user and policies are never created, yet the script ends with exit 0 and yonote starts anyway
the s3-client service runs mc once right after the MinIO container starts. depends_on waits only for the container to start, not for MinIO to accept connections. If MinIO isn't ready, the bucket, user and policies are never created, yet the script ends with exit 0 and yonote starts anyway
stuart.armstrong marked this conversation as resolved
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
@@ -0,0 +1,145 @@########## Обязательные переменные ##########KC_CLIENT_SECRET is missing here
@@ -0,0 +33,4 @@MINIO_YNT_HOST=s3.domain.ruMINIO_ADMIN_YNT_HOST=s3-admin.domain.ruMINIO_YNT_HOST_PROTOCOL=http://MINIO_YNT_URL=${MINIO_YNT_HOST}${MINIO_YNT_HOST_PROTOCOL}It seems to me that MINIO_YNT_HOST and MINIO_YNT_HOST_PROTOCOL are mixed up here
@@ -0,0 +99,4 @@MINIO_ADMIN_PASSWORD: ${MINIO_ADMIN_PASSWORD}entrypoint: >/bin/sh -c "/usr/bin/mc config host add myminio http://minio:9000 ${MINIO_ADMIN_USERNAME} ${MINIO_ADMIN_PASSWORD};the s3-client service runs mc once right after the MinIO container starts. depends_on waits only for the container to start, not for MinIO to accept connections. If MinIO isn't ready, the bucket, user and policies are never created, yet the script ends with exit 0 and yonote starts anyway