<p>At the moment the <code>docker login</code> and <code>docker push</code> commands are only available to Pipelines Alpha members.</p>

<p>You can read about the features available to Alpha at "<a href="https://confluence.atlassian.com/bitbucket/pipelines-alpha-877358733.html" rel="nofollow noreferrer">Pipelines Alpha</a>".</p>

<p>In order to participate, the above link includes instructions on how you can opt-in to the added functionality.</p>

<p>Personally I received an e-mail from Atlassian a day after signing up saying my projects now include Alpha features. So this feature works in my pipelines without any issues.</p>

CC BY-SA 3.0
2017-04-05T13:49:33.383Z
`Pipelines Alpha` - `Your response has been recorded.` I will accept the answer, when the issue is solved, i.e. when docker runs in our repository.
030
CC BY-SA 3.0
2017-04-05T13:43:46.417Z
2017-04-06T07:34:35.917Z
2017-04-06T07:34:35.917Z
Evgeny Zislis
<p><strong>Aim</strong></p>

<p>to login to a private docker registry using BitBucket pipelines.</p>

<p><strong>Attempt</strong></p>

<p>Based on <a href="https://confluence.atlassian.com/bitbucket/running-docker-commands-in-bitbucket-pipelines-879254331.html" rel="nofollow noreferrer">this</a> documentation the following bitbucket-pipelines.yml:</p>

<pre><code>image: docker:latest

pipelines:
  default:
    - step:
        script:
          - docker login -u $D_REGISTRY_USER -p $D_REGISTRY_PASS $D_REGISTRY_URL

options:
  docker: true
</code></pre>

<p>was created. When BitBucket pipelines run this it results in:</p>

<pre><code>+ docker login -u $DOCKER_REGISTRY_USERNAME -p $DOCKER_REGISTRY_PASSWORD 
$DOCKER_REGISTRY_URL
Warning: failed to get default registry endpoint from daemon 
(Error response from daemon: authorization denied by plugin pipelines: Command 
not supported.). 
Using system default: https://index.docker.io/v1/
Error response from daemon: authorization denied by plugin pipelines: Command 
not supported.
</code></pre>

<docker><bitbucket>
Why does `docker-login` fail in BitBucket pipelines?
030
# Why does `docker-login` fail in BitBucket pipelines?

(Asked by: username_0 on 2017-04-05)

Aim
to login to a private docker registry using BitBucket pipelines.
Attempt
Based on this documentation the following bitbucket-pipelines.yml:
image: docker:latest

pipelines:
  default:
    - step:
        script:
          - docker login -u $D_REGISTRY_USER -p $D_REGISTRY_PASS $D_REGISTRY_URL

options:
  docker: true

was created. When BitBucket pipelines run this it results in:
+ docker login -u $DOCKER_REGISTRY_USERNAME -p $DOCKER_REGISTRY_PASSWORD 
$DOCKER_REGISTRY_URL
Warning: failed to get default registry endpoint from daemon 
(Error response from daemon: authorization denied by plugin pipelines: Command 
not supported.). 
Using system default: https://index.docker.io/v1/
Error response from daemon: authorization denied by plugin pipelines: Command 
not supported.

**Tags:** docker, bitbucket


---

## 1 answers

### Answer by username_1 on 2017-04-05. Score: 4 | Accepted answer

At the moment the `docker login` and `docker push` commands are only available to Pipelines Alpha members.

You can read about the features available to Alpha at "[Pipelines Alpha](https://confluence.atlassian.com/bitbucket/pipelines-alpha-877358733.html)".

In order to participate, the above link includes instructions on how you can opt-in to the added functionality.

Personally I received an e-mail from Atlassian a day after signing up saying my projects now include Alpha features. So this feature works in my pipelines without any issues.

> **Comments:**
> **username_0**: `Pipelines Alpha` - `Your response has been recorded.` I will accept the answer, when the issue is solved, i.e. when docker runs in our repository.  

---

