-
Notifications
You must be signed in to change notification settings - Fork 318
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
Minio rejects valid hostnames #760
Comments
@dwhitlow Thanks for filing this issue. We will take a look at it. |
Praveenrajmani
added a commit
to Praveenrajmani/minio-py
that referenced
this issue
May 14, 2019
For eg, `minio_server` should be treated as valid hostnames. Fixes minio#760
Praveenrajmani
added a commit
to Praveenrajmani/minio-py
that referenced
this issue
May 15, 2019
For eg, `minio_server` should be treated as valid hostname. Fixes minio#760
Praveenrajmani
added a commit
to Praveenrajmani/minio-py
that referenced
this issue
May 15, 2019
For eg, `minio_server` should be treated as valid hostname. Fixes minio#760
Praveenrajmani
added a commit
to Praveenrajmani/minio-py
that referenced
this issue
May 15, 2019
For eg, `minio_server` should be treated as valid hostname. Fixes minio#760
Praveenrajmani
added a commit
to Praveenrajmani/minio-py
that referenced
this issue
May 15, 2019
For eg, `minio_server` should be treated as valid hostname. Fixes minio#760
nitisht
pushed a commit
that referenced
this issue
May 16, 2019
For eg, `minio_server` should be treated as valid hostname. Fixes #760
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Minio python library rejects hostnames with underscores in them. Since this is a standard separator for docker container names, this causes problems when trying to run Minio as part of a docker compose setup.
For example, with a linked container named
minio_server
, this python session should not raise an error:The text was updated successfully, but these errors were encountered: