ERROR: for boulder Container command not found or does not exist.

[elric....@gmail.com]

Yesterday I updated my system to Fedora 24. I then installed a local copy of go1.5.4.linux-amd64. Finally, I cloned Boulder. When I issue "docker-compose up" I see the following error:

Recreating 710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_boulder_boulder_1

ERROR: for boulder  Container command not found or does not exist.

Traceback (most recent call last):

  File "/usr/bin/docker-compose", line 9, in <module>

    load_entry_point('docker-compose==1.7.1', 'console_scripts', 'docker-compose')()

  File "/usr/lib/python2.7/site-packages/compose/cli/main.py", line 63, in main

    log.error(e.msg)

AttributeError: 'ProjectError' object has no attribute 'msg'

For the record, here are some versions.

go version

go version go1.5.4 linux/amd64

docker version

Client:

 Version:         1.10.3

 API version:     1.22

 Package version: docker-common-1.10.3-54.gite03ddb8.fc24.x86_64

 Go version:      go1.6.3

 Git commit:      e03ddb8/1.10.3

 Built:           

 OS/Arch:         linux/amd64

Server:

 Version:         1.10.3

 API version:     1.22

 Package version: docker-common-1.10.3-54.gite03ddb8.fc24.x86_64

 Go version:      go1.6.3

 Git commit:      e03ddb8/1.10.3

 Built:           

 OS/Arch:         linux/amd64

docker-compose version

docker-compose version 1.7.1, build 6c29830

docker-py version: 1.8.1

CPython version: 2.7.12

OpenSSL version: OpenSSL 1.0.2j-fips  26 Sep 2016

[Patrick Figel]

This seems to be a bug in docker-compose[1]. Should be fixed in
docker-compose >= 1.8.0. I'd suggest switching to Docker's Fedora
repo[2] if 1.7.1 is what Fedora itself is shipping.

[1]: https://github.com/docker/compose/issues/3432
[2]: https://docs.docker.com/engine/installation/linux/fedora/

[elric....@gmail.com]

Thanks. I'll give this a try.

[elric....@gmail.com]

This seems to have progressed the process, but I'm still getting an error.

Recreating 710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_710ed7c8d52a_boulder_boulder_1

ERROR: for boulder  invalid header field value "oci runtime error: container_linux.go:247: starting container process caused \"chdir to cwd (\\\"/go/src/github.com/letsencrypt/boulder\\\") set in config.json failed: no such file or directory\"\n"

Traceback (most recent call last):

  File "/usr/bin/docker-compose", line 9, in <module>

    load_entry_point('docker-compose==1.7.1', 'console_scripts', 'docker-compose')()

  File "/usr/lib/python2.7/site-packages/compose/cli/main.py", line 63, in main

    log.error(e.msg)

AttributeError: 'ProjectError' object has no attribute 'msg'

On Friday, November 4, 2016 at 12:15:34 PM UTC-7, Patrick Figel wrote:

[elric....@gmail.com]

For the record here is the **validated** "docker-compose config". Of note is the host system GOPATH in the boulder volumes section. It is both set and valid.

docker-compose config

networks: {}

services:

  bhsm:

    command: /usr/local/bin/pkcs11-daemon /usr/lib/softhsm/libsofthsm.so

    environment:

      PKCS11_DAEMON_SOCKET: tcp://0.0.0.0:5657

    expose:

    - 5657

    image: letsencrypt/boulder-tools:2016-10-19

    network_mode: bridge

  bmysql:

    command: mysqld --bind-address=0.0.0.0

    environment:

      MYSQL_ALLOW_EMPTY_PASSWORD: 'yes'

    image: mariadb:10.1

    logging:

      driver: none

    network_mode: bridge

  boulder:

    build:

      context: /home/user/boulder

      dockerfile: Dockerfile

    environment:

      FAKE_DNS: 127.0.0.1

      PKCS11_PROXY_SOCKET: tcp://boulder-hsm:5657

    extra_hosts:

      boulder: 127.0.0.1

      le.wtf: 127.0.0.1

    links:

    - bhsm:boulder-hsm

    - bmysql:boulder-mysql

    - brabbitmq:boulder-rabbitmq

    network_mode: bridge

    ports:

    - 4000:4000

    - 4002:4002

    - 4003:4003

    - 4500:4500

    - 8000:8000

    - 8001:8001

    - 8002:8002

    - 8003:8003

    - 8004:8004

    - 8055:8055

    - 9380:9380

    - 9381:9381

    volumes:

    - /home/user/golang:/go:rw

    - /tmp:/tmp:rw

  brabbitmq:

    environment:

      RABBITMQ_NODE_IP_ADDRESS: 0.0.0.0

    image: rabbitmq:3

    logging:

      driver: none

    network_mode: bridge

version: '2.0'

volumes: {}

[elric....@gmail.com]

For the record I also see the same result with the latest docker compose:

docker-compose version 1.9.0-rc3, build fcd38d3

docker-py version: 1.10.6

CPython version: 2.7.9

OpenSSL version: OpenSSL 1.0.1t  3 May 2016

On Friday, November 4, 2016 at 12:42:39 PM UTC-7, elric....@gmail.com wrote: