You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create Bucket
forward_port command: kubectl port-forward --address=0.0.0.0 --namespace magasin-tenant svc/myminio-hl 9000:9000
Waiting for port to be open...
Port ready.
Forwarding from 0.0.0.0:9000 -> 9000
mc command: mc admin info myminio --insecure
The command stays in mc admin info myminio --insecure indefinitely.
The text was updated successfully, but these errors were encountered:
Tested running kubectl port-forward --namespace magasin-tenant svc/myminio-hl 9000:9000, that is removing `--address=0.0.0.0
And in another terminal run
mag minio add bucket
Which resulted in success:
mag minio add bucket
Create Bucket
forward_port command: kubectl port-forward --address=0.0.0.0 --namespace magasin-tenant svc/myminio-hl 9000:9000
Waiting for port to be open...
Port ready.
Forwarding from 0.0.0.0:9000 -> 9000
mc command: mc admin info myminio --insecure
alias check successful
mc command:mc mb myminio/magasin-13oe2 --insecure
Bucket created successfully `myminio/magasin-13oe2`.
--address=0.0.0.0 was added for supporting the use of the docker image of magsh image, an image that includes all the commands required by magasin and currently in experimental mode (https://github.com/unicef/magasin/tree/main/magsh)
What may happen is that there is some security setup in minio that prevents to listen to all addresses.
Further research
Why --address=0.0.0.0 issue with minio services do not accept it.
Test removing --address=0.0.0.0 from mag and test to run the image in host mode.
The command stays in
mc admin info myminio --insecure indefinitely.
The text was updated successfully, but these errors were encountered: