unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /opt/atlassian/pipe

[kdao_dev]

I would like to use bitbucket pipelines. I configure pipelines file but i have this error: 

unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /opt/atlassian/pipelines/agent/build/Dockerfile: no such file or directory

here is my config file:

image: maven:3.3.9

options:
  docker: true
  
pipelines:
  branches:
    develop:
      - step:
          caches:
            - maven
          script:
            - export IMAGE_NAME=$DOCKER_HUB_USERNAME/$DOCKER_HUB_APP_NAME:$BITBUCKET_COMMIT      
            - docker build -t $IMAGE_NAME .
            - docker login --username $DOCKER_HUB_USERNAME --password $DOCKER_HUB_PASSWORD
            - docker push $IMAGE_NAME
          services:
            - database

definitions:
  services:
    database:
      image: mysql
      environment:
        MYSQL_ROOT_PASSWORD: password

Any help please!

[Shojibur Rahman (Shoji)]

Hey guys, i was having similar issue - 

What i realize is that, my dockerfile name was DockerFile [in the repo] but bitbucket pipeline is looking for Dockerfile. 

If this is the case just rename DockerFile to Dockerfile 

Thanks me later 

[mohit Mishra]

anyone got any ans for ths issue ?

[Alan Cooper]

This is often actually a file not found error - check you've actually committed & pushed your Dockerfile to the bitbucket repo properly and it's correctly named and referenced.

[jmoratat]

I have the same issue... and I have the DockerFile in root dir (working space in Pipeline).

¿Any idea?

[krzysztofmejka]

One suggestion - try adding `ls -lR` to one of your build steps. Perhaps you are actually missing the file in the folder where the build is run?

This helped me with my problems.

[Deleted user]

I've got the same issue, we only copied the pipeline example from bitbucket and doesn't work.

[krzysztofmejka]

I've got the same problem. @SeanHashi @kdao_dev did you find any solution?

[SeanHashi]

I am having the same issue. 

All I did was use the default docker pipeline script (and swapped out the placeholders) and I am getting the same error.