<p>Since I do not currently have access to a server with Centos installed, I tested my soultion on Ubuntu 20.04. That being said, the whole point of using Docker is to make applications distribution-agnostic, so it should work on Centos as well.</p>
<p>You're getting an <code>image does not exist</code> error, because the image you specified does not, in fact, exist. There is a typo in one line of the README file provided on Docker Hub and you happened to use that line when writing your Compose file.</p>
<p>That being said, incorect image name is not your only issue. You have not specified a volume for your Bitbucket installation, meaning all of your data will be lost if the container is destroyed. Furthermore, the only way to backup a dockerized Bitbucket installation is to use method described <a href="https://confluence.atlassian.com/display/BitbucketServer/Using+Bitbucket+Server+DIY+Backup" rel="nofollow noreferrer">here</a>, which requires using external database.</p>
<p>With that in mind the minimal Compose file for Bitbucket is:</p>
<pre><code>version: '3.3'
services:
  bitbucket:
    hostname: bitbucket
    image: atlassian/bitbucket-server:latest
    environment:
     - JDBC_DRIVER=org.postgresql.Driver
     - JDBC_USER=bitbucketuser
     - JDBC_PASSWORD=jellyfish
     - JDBC_URL=jdbc:postgresql://db:5432/bitbucket
    volumes:
      - bitbucket_data:/var/atlassian/application-data/bitbucket
    ports:
      - 7990:7990
      - 7999:7999
    depends_on:
      - db
  db:
    hostname: db
    image: postgres:11.2-alpine
    command: -c 'max_prepared_transactions=64'
    environment:
     - POSTGRES_USER=bitbucketuser
     - POSTGRES_PASSWORD=jellyfish
     - POSTGRES_DB=bitbucket
    volumes:
     - db_data:/var/lib/postgresql/data  
volumes:
  bitbucket_data:
  db_data:
</code></pre>
<p>That can be further extended with httpd or nginx service used as a reverse proxy, which could also be used to enable HTTPS connections to your Bitbucket instance and an Elasticsearch service to replace the embedded one as well as an email server for Bitbucket to use to send various notifications to users.</p>
<p>I would definitely recommend the SSL-enabled reverse proxy and email server for production. Elasticsearch server is only necessary if you want to run Bitbucket cluster rather than a single instance.</p>

CC BY-SA 4.0
2020-08-04T15:40:23.157Z
I'm amazed how they have a typo in the official document :) I will test later what you wrote. tnx! BTW, here I see it with the correct syntax: https://hub.docker.com/r/atlassian/bitbucket-server/tags?page=1
arielma
CC BY-SA 4.0
2020-08-04T13:12:19.777Z
2020-08-04T13:25:10.080Z
2020-08-04T13:25:10.080Z
Konrad Botor
<p>I'm trying to run the below composefile on centos7:</p>
<pre><code>version: &quot;3.3&quot;
services:

  bitbucket:
    image: atlassian/bitbucket:latest
    ports:
      - 7990:7990
      - 7999:7999
    networks:
      - my-app-net
networks:
  my-app-net:
    driver: bridge
</code></pre>
<p>But it fails to install it. I took the info from here:
<a href="https://hub.docker.com/r/atlassian/bitbucket-server/" rel="nofollow noreferrer">https://hub.docker.com/r/atlassian/bitbucket-server/</a>
did someone manage to install it as a container on Centos?</p>

CC BY-SA 4.0
2020-08-03T21:44:23.897Z
First of all, what you posted is a Compose file, not a Dockerfile. Second, what do you mean through Vagrant? Vagrant cannot use a Compose file by itself. Post some more details, including Vagrantfile and any errors, please.
Konrad Botor
CC BY-SA 4.0
2020-08-04T03:50:06.183Z
I clarified the question. Vagrant has nothing to do with it, so you can ignore it. the error I'm getting is `image does not exist`
arielma
<docker-compose><containers><bitbucket><centos>
Is it possible to install bitbucket container on Centos?
arielma
# Is it possible to install bitbucket container on Centos?

(Asked by: username_0 on 2020-08-03)

I'm trying to run the below composefile on centos7:
version: "3.3"
services:

  bitbucket:
    image: atlassian/bitbucket:latest
    ports:
      - 7990:7990
      - 7999:7999
    networks:
      - my-app-net
networks:
  my-app-net:
    driver: bridge

But it fails to install it. I took the info from here:
https://hub.docker.com/r/atlassian/bitbucket-server/
did someone manage to install it as a container on Centos?

**Tags:** docker-compose, containers, bitbucket, centos

> **Comments:**
> **username_1**: First of all, what you posted is a Compose file, not a Dockerfile. Second, what do you mean through Vagrant? Vagrant cannot use a Compose file by itself. Post some more details, including Vagrantfile and any errors, please.  
> **username_0**: I clarified the question. Vagrant has nothing to do with it, so you can ignore it. the error I'm getting is `image does not exist`  

---

## 1 answers

### Answer by username_1 on 2020-08-04. Score: 1 | Accepted answer

Since I do not currently have access to a server with Centos installed, I tested my soultion on Ubuntu 20.04. That being said, the whole point of using Docker is to make applications distribution-agnostic, so it should work on Centos as well.
You're getting an image does not exist error, because the image you specified does not, in fact, exist. There is a typo in one line of the README file provided on Docker Hub and you happened to use that line when writing your Compose file.
That being said, incorect image name is not your only issue. You have not specified a volume for your Bitbucket installation, meaning all of your data will be lost if the container is destroyed. Furthermore, the only way to backup a dockerized Bitbucket installation is to use method described here, which requires using external database.
With that in mind the minimal Compose file for Bitbucket is:
version: '3.3'
services:
  bitbucket:
    hostname: bitbucket
    image: atlassian/bitbucket-server:latest
    environment:
     - JDBC_DRIVER=org.postgresql.Driver
     - JDBC_USER=bitbucketuser
     - JDBC_PASSWORD=jellyfish
     - JDBC_URL=jdbc:postgresql://db:5432/bitbucket
    volumes:
      - bitbucket_data:/var/atlassian/application-data/bitbucket
    ports:
      - 7990:7990
      - 7999:7999
    depends_on:
      - db
  db:
    hostname: db
    image: postgres:11.2-alpine
    command: -c 'max_prepared_transactions=64'
    environment:
     - POSTGRES_USER=bitbucketuser
     - POSTGRES_PASSWORD=jellyfish
     - POSTGRES_DB=bitbucket
    volumes:
     - db_data:/var/lib/postgresql/data  
volumes:
  bitbucket_data:
  db_data:

That can be further extended with httpd or nginx service used as a reverse proxy, which could also be used to enable HTTPS connections to your Bitbucket instance and an Elasticsearch service to replace the embedded one as well as an email server for Bitbucket to use to send various notifications to users.
I would definitely recommend the SSL-enabled reverse proxy and email server for production. Elasticsearch server is only necessary if you want to run Bitbucket cluster rather than a single instance.

> **Comments:**
> **username_0**: I'm amazed how they have a typo in the official document :) I will test later what you wrote. tnx! BTW, here I see it with the correct syntax: https://hub.docker.com/r/atlassian/bitbucket-server/tags?page=1  

---

