celery - Different behavior between built and pulled docker image--clock errors? -
i use docker , docker-compose deploy application. i've built images on server (with docker-compose build) transitioned building them on local machine , pushing them docker hub, pulling them onto remote machine.
since making change, i've seen strange new error in 1 of containers. compose file defines flask app , celery worker use same codebase , dockerfile (with different entrypoints). since making change, following error every time start celery worker:
app_worker_1: [2017-07-28 16:47:35,400: warning/mainprocess] substantial drift celery@worker.fb71685cd5a7 may mean clocks out of sync. current drift 48 seconds. [orig: 2017-07-28 16:47:27.338937 recv: 2017-07-28 16:46:39.150362] i've never seen error before, , goes away if container built on server.
version: '2' services: flask: restart: image: me/flask command: /home/app/start_app.sh env_file: ./flask/dev.env worker: restart: image: me/flask command: /home/app/start_worker.sh env_file: ./flask/dev.env before, looked this:
version: '2' services: flask: restart: build: ./flask command: /home/app/start_app.sh env_file: ./flask/dev.env worker: restart: build: ./flask command: /home/app/start_worker.sh env_file: ./flask/dev.env server running ubuntu 16.04. i'm building images on laptop, running max os x. docker daemon on server 17.06.0-ce.
Comments
Post a Comment