Build issue - docker-compose

[webyahoo]

Tried the installation on multiple Docker environments and run into similar issues:

1. On AWS ubuntu instance, run the docker-compose, and get the following error message:

ubuntu@ip-abc:~/dev/ifc-pipeline$ sudo docker-compose up -d

Step 21/31 : COPY application/static /www/static/
---> Using cache
---> e2c4d49566da
Step 22/31 : COPY application/bimsurfer/bimsurfer /www/static/bimsurfer
ERROR: Service 'frontend' failed to build: COPY failed: stat /var/lib/docker/tmp/docker-builder365633164/application/bimsurfer/bimsurfer: no such file or directory

[webyahoo]

Looks like the source Docker file directory does not exist. If the entire installation guide to the repository is only 2 lines, and I ran into multiple issues building from the source, how can I proceed from here?

ubuntu@ip-abce:~/dev/ifc-pipeline$ sudo ls /var/lib/docker/tmp/docker-builder365633164/
ls: cannot access '/var/lib/docker/tmp/docker-builder365633164/': No such file or directory

Thanks.

[aothms]

It's a git submodule. So you need to clone with --recursive or do a git submodule init && git submodule update after checkout. Sorry for the late reply.

[webdada]

Thanks @aothms. I run git commands you suggested and it updated the application submodule with new files.

And the I run docker-compose and it completed (see log below). But no docker machines were created. If I run:
$docker-machine ls
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
It show no docker machines are active.

// console output:

.....
Step 30/31 : COPY application/queue.conf /etc/supervisord.conf
---> Using cache
---> 45bb7fd61765
Step 31/31 : WORKDIR /www
---> Using cache
---> 34926a444dc2
Successfully built 34926a444dc2
Successfully tagged ifc-pipeline_worker:latest
WARNING: Image for service worker was built because it did not already exist. To rebuild this image you must use docker-compose build or docker-compose up --build.
Creating ifc-pipeline_certbot_1 ... done
Creating ifc-pipeline_db_1 ... done
Creating ifc-pipeline_redis_1 ... done
Creating ifc-pipeline_frontend_1 ... done
Creating ifc-pipeline_worker_1 ... done
Creating ifc-pipeline_nginx_1 ... done

[webdada]

As I am testing on the AWS ubuntu machine, I am expecting to use the localhost.
How to we access the web application via https//<ip_address>, or https://localhost?

ubuntu@ip-abc:~/dev/ifc-pipeline$ sudo ./init.sh def.com
docker: Error response from daemon: driver failed programming external connectivity on endpoint mystifying_jepsen (4df45da3943a183f934b61542ea03741925f9c49d4e0e3ba7da523ed1d9e4220): Bind for 0.0.0.0:80 failed: port is already allocated.

[aothms]

But no docker machines were created

I'm not familiar with docker machine. docker ps should list the running containers. If you think there is some benefit to this project in using docker machine, feel free to send a Pull Request.

Bind for 0.0.0.0:80 failed: port is already allocated.

init.sh starts a certbot image on port 80 for the https certificate. So make sure no other hosts are running (also not the pipeline docker compose (run docker-compose down).

https//<ip_address>,

That doesn't exist afaict. httpS is always tied to a domain name. But you can use http://[ip-address]. If the compose is running.

Run docker-compose logs to see any issues.

[Gubanov-482022]

Поскольку я тестирую на машине AWS ubuntu, я ожидаю использовать localhost. Как мы можем получить доступ к веб-приложению через https//<ip_address>, или https://localhost?

ubuntu@ip-abc:~/dev/ifc-pipeline$ sudo ./init.sh def.com docker: Ответ на ошибку от демона: драйвер не смог запрограммировать внешнее подключение на конечной точке mystifying_jepsen (4df45da3943a183f934b61542ea03741925f9c49d4e0e3ba7da523ed1d9e4220): Привязка для 0.0.0.0: 80 не удалось: порт уже выделен.

Поскольку я тестирую на машине AWS ubuntu, я ожидаю использовать localhost. Как мы можем получить доступ к веб-приложению через https//<ip_address>, или https://localhost?

ubuntu@ip-abc:~/dev/ifc-pipeline$ sudo ./init.sh def.com docker: Ответ на ошибку от демона: драйвер не смог запрограммировать внешнее подключение на конечной точке mystifying_jepsen (4df45da3943a183f934b61542ea03741925f9c49d4e0e3ba7da523ed1d9e4220): Привязка для 0.0.0.0: 80 не удалось: порт уже выделен.

hello. Have you solved this problem?