Compose: `GLIBC_2.14' not found

[michaelknurr]

Description of the issue

When upgrading docker compose to a version later than 1.19.0 i get an error

$ sudo curl -L https://github.com/docker/compose/releases/download/1.20.0/docker-compose-`uname -s`-`uname -m` -o /usr/local/bin/docker-compose

$ docker-compose --version
docker-compose: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /tmp/_MEIb0wktP/libz.so.1)



md5-807549dd5273876b491041542a2ddbbd



$ sudo curl -L https://github.com/docker/compose/releases/download/1.19.0/docker-compose-`uname -s`-`uname -m` -o /usr/local/bin/docker-compose



md5-b93d6843c439254477c24c02057237d2



$ docker-compose --version
docker-compose version 1.19.0, build 9e633ef



md5-0dd9e619f05ee6ce4a88ef92460425a3



Output of "docker-compose version"



md5-b93d6843c439254477c24c02057237d2



Output of "docker version"



md5-fa48ddb92d104840ae8b27050b280988



Output of "docker-compose config"

Additional information

it seems like there is a possible relation to #102 https://github.com/docker/compose/issues/102

OS version / distribution, docker-compose install method, etc.

[shin-]

This probably means you need a more recent version of glibc. Related: https://unix.stackexchange.com/questions/176489/how-to-update-glibc-to-2-14-in-centos-6-5

Alternatively, you can install the newer versions using pip.

[rainabba]

I just hit this and after investigating, realized that my docker-compose.override.yml had a volume that effectively caused my containers node_modules folder to reflect my local (not the built one) and so my container was trying to execute a binary built off different dependencies that didn't play well.

Insidious :)