Uploaded image for project: 'Project Quay'
  1. Project Quay
  2. PROJQUAY-260

Could not parse Dockerfile: file with no instructions

XMLWordPrintable

    • Hide

      Host OS:
      CentOS 7.7.1908 (Core)
      3.10.0-1062.12.1.el7.x86_64

      Docker Packages:
      docker-1.13.1-108.git4ef4b30.el7.centos.x86_64
      docker-common-1.13.1-108.git4ef4b30.el7.centos.x86_64
      docker-client-1.13.1-108.git4ef4b30.el7.centos.x86_64

      Container Images:
      quay.io/redhat/quay:3.2.0
      quay.io/redhat/quay-builder:3.2.0

      Docker Commands:

      docker run --restart=always -p 443:8443 -p 80:8080 --sysctl net.core.somaxconn=4096 --privileged=true -v /mnt/quay/config:/conf/stack:Z -v /mnt/quay/storage:/datastorage:Z -d quay.io/redhat/quay:v3.2.0

      docker run --restart on-failure -d -e SERVER=wss://containers.example.com --privileged=true -v /var/run/docker.sock:/var/run/docker.sock quay.io/redhat/quay-builder:v3.2.0
      Show
      Host OS: CentOS 7.7.1908 (Core) 3.10.0-1062.12.1.el7.x86_64 Docker Packages: docker-1.13.1-108.git4ef4b30.el7.centos.x86_64 docker-common-1.13.1-108.git4ef4b30.el7.centos.x86_64 docker-client-1.13.1-108.git4ef4b30.el7.centos.x86_64 Container Images: quay.io/redhat/quay:3.2.0 quay.io/redhat/quay-builder:3.2.0 Docker Commands: docker run --restart=always -p 443:8443 -p 80:8080 --sysctl net.core.somaxconn=4096 --privileged=true -v /mnt/quay/config:/conf/stack:Z -v /mnt/quay/storage:/datastorage:Z -d quay.io/redhat/quay:v3.2.0 docker run --restart on-failure -d -e SERVER=wss://containers.example.com --privileged=true -v /var/run/docker.sock:/var/run/docker.sock quay.io/redhat/quay-builder:v3.2.0
    • 0

      Attempting to use a valid Dockerfile (or archive with valid Dockerfile) to build an image with the "quay-builder:latest" container results in the following error message within the "quay" UI:

      Could not find or parse Dockerfile: Empty Dockerfile

      The "quay-builder" container shows the following:

      time="2020-02-06T16:00:31Z" level=info msg="decoded build args: rpc.BuildArgs{BuildPackage:\"https://containers.example.com/userfiles/cbbf1bc6-e443-4e40-a12d-aea16161d3eb\", Context:\"/\", DockerfilePath:\"Dockerfile\", Repository:\"superuser/test\", Registry:\"containers.example.com\", PullToken:\"REMOVED", PushToken:\"REMOVED", TagNames:[]string{\"latest\"}, Git:(*rpc.BuildArgsGit)(nil), BaseImage:rpc.BuildArgsBaseImage{Username:\"\", Password:\"\"}}"
time="2020-02-06T16:00:31Z" level=info msg="connecting to docker host: unix:///var/run/docker.sock"
time="2020-02-06T16:00:31Z" level=info msg="connected to docker host: unix:///var/run/docker.sock"
time="2020-02-06T16:00:31Z" level=info msg="downloading buildpack: https://containers.example.com/userfiles/cbbf1bc6-e443-4e40-a12d-aea16161d3eb"
time="2020-02-06T16:00:31Z" level=info msg="buildpack identified as plain"
time="2020-02-06T16:00:31Z" level=error msg="Could not parse Dockerfile: file with no instructions."
time="2020-02-06T16:00:31Z" level=info msg="build resulted in an error: Empty Dockerfile"
time="2020-02-06T16:00:31Z" level=info msg="determined final WAMP response URI for error (type: rpc.InvalidDockerfileError) 'Empty Dockerfile': io.quay.builder.dockerfileissue"

      The Dockerfile that I'm using is https://github.com/quay/quay/blob/master/Dockerfile . I've also tried several other valid Dockerfiles with the same result. The above file does exist and contains the contents of the Dockerfile that was uploaded via the UI.

      The docker host is CentOS 7.7 running both containers and is not behind an LB. The Quay config is very basic, but uses AWS hosted Postgres RDS and Redis. I've attached the Quay config file to this issue.

        1. config.yaml
          2 kB

            jschorr Joseph Schorr (Inactive)
            ehartsock Eric Hartsock (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: