RhodeCode Community Edition in Docker

Docker container for the RhodeCode Community Edition source code management platform.

RhodeCode provides Git, Subversion (svn) and Mercurial (hg) support.

WIP

This image is based on the previous work by darneta, updated to current versions and heavily modified.

PLEASE NOTE: I'm a new RhodeCode user so I'm still figuring out the best way to make this image work.

Set up

With Docker Compose

$ git --clone https://github.com/outlyer-net/docker-rhodecode-ce.git
$ cd docker-rhodecode-ce
$ docker-compose up -d

(optionally run docker-compose logs to see the initialisation log)

That's it.
Although you may want to customise the contents of the docker-compose.yaml file.

Tweaks

• The compose file will use named docker volumes by default, that will be created on the fly, it may be advisable to change those to bind mounts to ensure they aren't removed accidentally with docker volume prune.

• By default the compose file will use rhodecode as the name for the container and prefix for generated volumes' names (e.g. rhodecode_conf).
  This can be changed by setting the RHODECODE_CONTAINER_NAME environment variable before running docker-compose, e.g.:

  $ env RHODECODE_CONTAINER_NAME=reposerver docker-compose up -d
  

Without Docker Compose

To preserve data even when the container is destroyed you must make sure to mount at least these paths:

• /repos → The actual repositories
• /rhodecode → RhodeCode configuration and logs

Here's an example command-line to spin the container (long options are used for increased readability), named volumes are used in this example to let Docker handle volume creation (care must be taken not to unadvertedly remove the volumes or data will be lost):

$ docker run --detach \
    --publish 8080:8080 \
    --volume rhodecode_repos:/repos \
    --volume rhodecode_data:/rhodecode \
    --name rhodecode \
    outlyernet/rhodecode-ce

Administrator login

By default the RhodeCode administrator is created with username admin and password secret.
Both can be changed from the administration panel after login.

Database

By default an sqlite database is used (RhodeCode doesn't support unattended installs with any other database), but it can be set up afterwards. An override Docker Compose file is provided to set up a database container alongside RhodeCode, but the post-install set up is not automated, you'll have to adjust it yourself.

$ docker-compose -f docker-compose.yaml -f docker-compose.mariadb.yaml up
$ # must change the RhodeCode database here

Exposed ports

• 8080: HTTP port on which RhodeCode serves. This port is published by default when using docker-compose.
• 3690: VCS port. This port isn't published by default.

Running as an unprivileged user / Avoiding file permission issues

By default the image runs commands as root.
It contains some workarounds to allow running as a different user (hence creating all files with appropriate permissions), but you'll have to do some preparations.

Below are example commands for one of way to set things up, in this example we want to run with UID 1000 and GID 1000.

Using bind mounts

Create mount points, run a temporary container without actually running RhodeCode, and initialise the volumes.
Note only the /rhodecode volume has to be initialised since /repos is initially empty.

$ mkdir data repos
$ docker run --rm -it \
    -v $PWD/data:/rhodecode \
    --entrypoint /bin/bash \
    --user 1000:1000 outlyernet/rhodecode-ce
I have no name!@dockerid:/$ /reset_image
I have no name!@dockerid:/$ exit

At this point ./data is ready to be used and the container can be created normally. However to avoid errors you'll also have to mount the host's /etc/passwd and /etc/group so that the user and group names get resolved.

$ docker run --detach \
    -v $PWD/data:/rhodecode \
    -v $PWD/repos:/repos \
    -v /etc/passwd:/etc/passwd:ro \
    -v /etc/group:/etc/group:ro \
    --user 1000:1000 outlyernet/rhodecode-ce

Using Docker volumes

Do a first normal run as root so that the volumes are initialised automatically.

$ docker run --rm -it \
    -v rhodecode_data:/rhodecode \
    -v rhodecode_repos:/repos \
    outlyernet/rhodecode-ce

Interrupt the container (e.g. with CTRL+C), then run a new temporary container to adjust file permissions.

$ docker run --rm -it \
    -v rhodecode_data:/rhodecode \
    -v rhodecode_repos:/repos \
    ubuntu:18.04
root@dockerid:/# chown -R 1000.1000 /rhodecode /repos
root@dockerid:/# exit

At this point the rhodecode_data and rhodecode_repos volumes are ready to be used and the container can be created normally. However to avoid errors you'll also have to mount the host's /etc/passwd and /etc/group so that the user and group names get resolved.

$ docker run --detach \
    -v rhodecode_data:/rhodecode \
    -v rhodecode_repos:/repos \
    -v /etc/passwd:/etc/passwd:ro \
    -v /etc/group:/etc/group:ro \
    --user 1000:1000 outlyernet/rhodecode-ce

Links

• GitHub
• Docker Hub