Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add documentation for Bitbucket Pipelines #1439

Merged
merged 2 commits into from May 7, 2019
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
@@ -0,0 +1,26 @@
# Bitbucket Pipelines

To enable access to Docker in Bitbucket Pipelines, you need to add `docker` as a service on the step.

Furthermore, Ryuk needs to be turned off since Bitbucket Pipelines does not allow starting privileged containers (see [Disabling Ryuk](../../features/configuration.md#disabling-ryuk)). This can either be done by setting a repository variable in Bitbucket's project settings or by explicitly exporting the variable on a step.

In some cases the memory available to Docker needs to be increased.

Here is a sample Bitbucket Pipeline configuration that does a checkout of a project and runs maven:

```yml
image: maven:3.6.1

pipelines:
default:
- step:
script:
- export TESTCONTAINERS_RYUK_DISABLED=true
- mvn clean install
services:
- docker
definitions:
services:
docker:
memory: 2048
```
1 change: 1 addition & 0 deletions mkdocs.yml
Expand Up @@ -70,6 +70,7 @@ nav:
- supported_docker_environment/continuous_integration/dind_patterns.md
- supported_docker_environment/continuous_integration/circle_ci.md
- supported_docker_environment/continuous_integration/gitlab_ci.md
- supported_docker_environment/continuous_integration/bitbucket_pipelines.md
- supported_docker_environment/windows.md
- supported_docker_environment/logging_config.md
- Getting help: getting_help.md
Expand Down