GitLab lfs errors when using minio (Failed to transfer LFS object getaddrinfo: Name or service not known (SocketError))

Summary

When using GitLab lfs with minio, I am getting an error when the lfs objects are being uploaded.

Steps to reproduce

I am using omnibus with GitLab 10.4 (docker).

Here is my configuration.

gitlab_rails['lfs_enabled'] = true
gitlab_rails['lfs_object_store_enabled'] = true
gitlab_rails['lfs_object_store_background_upload'] = false
gitlab_rails['lfs_object_store_remote_directory'] = "my-directory-in-minio-which-is-a-gcs-bucket"
gitlab_rails['lfs_object_store_connection'] = {
   'provider' => 'AWS',
   'region' => 'eu-west-1',
   'aws_access_key_id' => 'mycompany',
   'aws_secret_access_key' => 'mykey',
   'host' => 'minio.mydomain.com',
   'endpoint' => "http://minio.mydomain.com:9000",
   'path_style' => false
}

I can verify that I can access http://minio.mydomain.com:9000 with browser and see my Google Cloud Storage buckets and everything works. I have verified that I can connect to service in the docker image via telnet minio.mydomain.com 9000.

Example Project

I haven't updated to the latest version of GitLab. This would take some time, but if you think it would fix this error, I'd be happy to.

What is the current bug behavior?

> gitlab-rake gitlab:lfs:migrate
I, [2018-04-06T18:21:01.505452 #9128]  INFO -- : Starting transfer of LFS files to object storage
E, [2018-04-06T18:21:01.849558 #9128] ERROR -- : Failed to transfer LFS object 55f8718109829bf506b09d8af615b9f107a266e19f7a311039d1035f180b22d4 with error: getaddrinfo: Name or service not known (SocketError)
E, [2018-04-06T18:21:01.861496 #9128] ERROR -- : Failed to transfer LFS object 12ac3b74ff3a229de7406c389dbec150de3a1033575b202303361698a1b6a2e4 with error: getaddrinfo: Name or service not known (SocketError)

What is the expected correct behavior?

I expected my new lfs objects to exist on my minio server, which is configured to point to my Google Cloud Storage.

Output of checks

Results of GitLab environment info

System information
System:
Proxy:          no
Current User:   git
Using RVM:      no
Ruby Version:   2.3.6p384
Gem Version:    2.6.13
Bundler Version:1.13.7
Rake Version:   12.3.0
Redis Version:  3.2.11
Git Version:    2.14.3
Sidekiq Version:5.0.5
Go Version:     unknown

GitLab information
Version:        10.4.3-ee
Revision:       6e627c8
Directory:      /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:     postgresql
DB Version:     9.6.5
URL:            https://lab.medxchange.com
HTTP Clone URL: https://lab.medxchange.com/some-group/some-project.git
SSH Clone URL:  git@lab.medxchange.com:some-group/some-project.git
Elasticsearch:  no
Geo:            no
Using LDAP:     no
Using Omniauth: no

GitLab Shell
Version:        5.11.0
Repository storage paths:
- default:      /var/opt/gitlab/git-data/repositories
Hooks:          /opt/gitlab/embedded/service/gitlab-shell/hooks
Git:            /opt/gitlab/embedded/bin/git

Results of GitLab application Check

Checking GitLab Shell ...

GitLab Shell version >= 5.11.0 ? ... OK (5.11.0)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by git:root, or git:git?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ... 
3/1 ... repository is empty
3/2 ... ok
1/4 ... ok
5/5 ... ok
1/6 ... ok
3/7 ... ok
8/8 ... ok
9/9 ... ok
1/10 ... ok
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Redis available via internal API: OK

Access to /var/opt/gitlab/.ssh/authorized_keys: OK
gitlab-shell self-check successful

Checking GitLab Shell ... Finished

Checking Sidekiq ...

Running? ... yes
Number of Sidekiq processes ... 1

Checking Sidekiq ... Finished

Reply by email is disabled in config/gitlab.yml
Checking LDAP ...

LDAP is disabled in config/gitlab.yml

Checking LDAP ... Finished

Checking GitLab ...

Git configured correctly? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... yes
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory exists? ... yes
Uploads directory has correct permissions? ... yes
Uploads directory tmp has correct permissions? ... yes
Init script exists? ... skipped (omnibus-gitlab has no init script)
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
Projects have namespace: ... 
3/1 ... yes
3/2 ... yes
1/4 ... yes
5/5 ... yes
1/6 ... yes
3/7 ... yes
8/8 ... yes
9/9 ... yes
1/10 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.5 ? ... yes (2.3.6)
Git version >= 2.7.3 ? ... yes (2.14.3)
Git user has default SSH configuration? ... yes
Active users: ... 5
Elasticsearch version 5.1 - 5.5? ... skipped (elasticsearch is disabled)

Checking GitLab ... Finished