php-fpm container can change source from debian to china?

[mouyong]

Info:

• Docker version ($ docker --version): Docker version 18.03.0-ce, build 0520e24302
• Laradock commit ($ git rev-parse HEAD): da8f0d0
• System info (Mac, PC, Linux): PC
• System info disto/version: WIN10

Issue:

---

docker-compose build php-fpm is slow very much in china

Expected behavior:

---

docker-compose build php-fpm can be fast

Reproduce:

---

don't have error.

Relevant Code:

// place a code sample here
.

php-fpm container can change source from debian to china?

php-fpm/debian.sources.list

deb http://mirrors.aliyun.com/debian/ stretch main non-free contrib
deb-src http://mirrors.aliyun.com/debian/ stretch main non-free contrib
deb http://mirrors.aliyun.com/debian-security stretch/updates main
deb-src http://mirrors.aliyun.com/debian-security stretch/updates main
deb http://mirrors.aliyun.com/debian/ stretch-updates main non-free contrib
deb-src http://mirrors.aliyun.com/debian/ stretch-updates main non-free contrib
deb http://mirrors.aliyun.com/debian/ stretch-backports main non-free contrib
deb-src http://mirrors.aliyun.com/debian/ stretch-backports main non-free contrib

Dockerfile

# If you're in China, or you need to change sources, will be set CHANGE_SOURCE to true in .env.

ADD debian.sources.list /etc/apt/debian.sources.list
ARG CHANGE_SOURCE=false
RUN if [ ${CHANGE_SOURCE} = true ]; then \
  mv /etc/apt/sources.list /etc/apt/sources.list.back && \
  mv /etc/apt/debian.sources.list /etc/apt/sources.list \
;fi

docker-compose.yml

        .
        .
        .
php-fpm:
      build:
        context: ./php-fpm
        args:
          - CHANGE_SOURCE=${CHANGE_SOURCE}
          - LARADOCK_PHP_VERSION=${PHP_VERSION}
          - LARADOCK_PHALCON_VERSION=${PHALCON_VERSION}
        .
        .
        .

[mouyong]

f64adc2

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

Hi again 👋 we would like to inform you that this issue has been automatically closed 🔒 because it had not recent activity during the stale period. We really really appreciate your contributions, and looking forward for more in the future 🎈.