{"id":15020625,"url":"https://github.com/ulm0/gitlab","last_synced_at":"2025-10-26T04:30:36.069Z","repository":{"id":53264440,"uuid":"120632635","full_name":"ulm0/gitlab","owner":"ulm0","description":"GitLab CE (Docker image) for ARM devices, this is a mirror repository of","archived":false,"fork":false,"pushed_at":"2021-04-05T01:48:22.000Z","size":183,"stargazers_count":187,"open_issues_count":0,"forks_count":22,"subscribers_count":11,"default_branch":"master","last_synced_at":"2025-02-06T06:16:44.884Z","etag":null,"topics":["arm","armhf","armv7","docker","gitlab","gitlab-ce","gitlab-docker","gitlab-mirror","raspberry","raspberry-pi-3","raspberrypi"],"latest_commit_sha":null,"homepage":"https://gitlab.com/ulm0/gitlab","language":"Shell","has_issues":false,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/ulm0.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2018-02-07T15:26:08.000Z","updated_at":"2024-12-20T15:22:30.000Z","dependencies_parsed_at":"2022-08-27T06:40:18.934Z","dependency_job_id":null,"html_url":"https://github.com/ulm0/gitlab","commit_stats":null,"previous_names":[],"tags_count":60,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ulm0%2Fgitlab","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ulm0%2Fgitlab/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ulm0%2Fgitlab/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ulm0%2Fgitlab/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/ulm0","download_url":"https://codeload.github.com/ulm0/gitlab/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":238258968,"owners_count":19442508,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["arm","armhf","armv7","docker","gitlab","gitlab-ce","gitlab-docker","gitlab-mirror","raspberry","raspberry-pi-3","raspberrypi"],"created_at":"2024-09-24T19:55:21.285Z","updated_at":"2025-10-26T04:30:35.710Z","avatar_url":"https://github.com/ulm0.png","language":"Shell","readme":"# GitLab CE for ARM\n\n[![pipeline status](https://gitlab.com/ulm0/gitlab/badges/master/pipeline.svg)](https://gitlab.com/ulm0/gitlab/commits/master) [![](https://images.microbadger.com/badges/version/ulm0/gitlab.svg)](https://microbadger.com/images/ulm0/gitlab \"Get your own version badge on microbadger.com\") [![](https://images.microbadger.com/badges/image/ulm0/gitlab.svg)](https://microbadger.com/images/ulm0/gitlab \"Get your own image badge on microbadger.com\") [![Docker Pulls](https://img.shields.io/docker/pulls/ulm0/gitlab.svg)](https://hub.docker.com/r/ulm0/gitlab/)\n\nGitLab CE for ARM is in Docker Hub:\n\n- [ulm0/gitlab](https://hub.docker.com/r/ulm0/gitlab/)\n\nThe GitLab Docker image is a monolithic image of GitLab running all the necessary services on a single container.\n\n**GitLab only offers the Community Edition for Raspbery Pi**, this Docker image is based on that one; in addition, **only stable builds are containerized**.\n\n### NOTES\n\n* This image provides default settings for it to work properly on ARM devices, which do not have a lot of RAM, you can review these settings [here](docker/assets/gitlab.rb) or use your own settings as explained in [Configure GitLab](#configure-gitlab). As a side note, *although is not advised,* you may still need to add a bit of SWAP (2GB recommended) to your device or have at least 2GB RAM, this can be achieved by using a USB Drive you have gathering dust somewhere; **DO NOT USE THE SD CARD FOR THIS TASK**.\n* This image does not apply sysctl parameters (see [wrapper file](docker/assets/wrapper#L90)), because it has been causing problems when starting in Docker Swarm, you can read the [reddit discussion](https://www.reddit.com/r/kubernetes/comments/7pr6r7/gitlab_ce_docker_image_for_arm/dtqemei/) about that. Get to the [Sysctl tunning](#sysctl-tunning) topic in order to know how to apply this on the host running GitLab.\n\n## The GitLab Docker image can be run in multiple ways:\n\n* [Run the image in Docker Engine](#run-the-image)\n* [Install GitLab using docker-compose](#install-gitlab-using-docker-compose)\n* [Install GitLab into a cluster](#install-gitlab-into-a-cluster)\n\n## Prerequisites\n\nDocker installation is required, see the [official installation docs](https://docs.docker.com/engine/installation/).\n\n## Run the image\n\nRun the image:\n\n```bash\ndocker run -d \\\n--hostname gitlab.example.com \\\n-p 443:443 -p 80:80 -p 22:22 \\\n--name gitlab \\\n--restart always \\\n-v /srv/gitlab/config:/etc/gitlab \\\n-v /srv/gitlab/logs:/var/log/gitlab \\\n-v /srv/gitlab/data:/var/opt/gitlab \\\nulm0/gitlab\n```\n\nThis will download and start a GitLab CE container and publish ports needed to\naccess SSH, HTTP and HTTPS. All GitLab data will be stored as subdirectories of\n`/srv/gitlab/`. The container will automatically `restart` after a system reboot.\n\nYou can now login to the web interface as explained in\n[After starting a container](#after-starting-a-container).\n\nIf you are on *SELinux* then run this instead:\n\n```bash\ndocker run -d \\\n--hostname gitlab.example.com \\\n-p 443:443 -p 80:80 -p 22:22 \\\n--name gitlab \\\n--restart always \\\n-v /srv/gitlab/config:/etc/gitlab:Z \\\n-v /srv/gitlab/logs:/var/log/gitlab:Z \\\n-v /srv/gitlab/data:/var/opt/gitlab:Z \\\nulm0/gitlab\n```\n\nThis will ensure that the Docker process has enough permissions to create the\nconfig files in the mounted volumes.\n\n## Where is the data stored?\n\nThe GitLab container uses host mounted volumes to store persistent data:\n\n| Local location | Container location | Usage |\n| -------------- | ------------------ | ----- |\n| `/srv/gitlab/data`  | `/var/opt/gitlab` | For storing application data |\n| `/srv/gitlab/logs`  | `/var/log/gitlab` | For storing logs |\n| `/srv/gitlab/config`| `/etc/gitlab`     | For storing the GitLab configuration files |\n\nYou can fine tune these directories to meet your requirements.\n\n## Configure GitLab\n\nThis container uses the official Omnibus GitLab package, so all configuration\nis done in the unique configuration file `/etc/gitlab/gitlab.rb`.\n\nTo access GitLab's configuration file, you can start a shell session in the\ncontext of a running container. This will allow you to browse all directories\nand use your favorite text editor:\n\n```bash\ndocker exec -it gitlab /bin/bash\n```\n\nYou can also just edit `/etc/gitlab/gitlab.rb`:\n\n```bash\ndocker exec -it gitlab vi /etc/gitlab/gitlab.rb\n```\n\nOnce you open `/etc/gitlab/gitlab.rb` make sure to set the `external_url` to\npoint to a valid URL.\n\nTo receive e-mails from GitLab you have to configure the\n[SMTP settings](https://gitlab.com/gitlab-org/omnibus-gitlab/tree/master/doc/settings/smtp.md) because the GitLab Docker image doesn't\nhave an SMTP server installed.\n\nYou may also be interested in [Enabling HTTPS](https://gitlab.com/gitlab-org/omnibus-gitlab/tree/master/doc/settings/nginx.md#enable-https).\n\nAfter you make all the changes you want, you will need to restart the container\nin order to reconfigure GitLab:\n\n```bash\ndocker restart gitlab\n```\n\n_**Note:** GitLab will reconfigure itself whenever the container starts._\n\nFor more options about configuring GitLab please check the\n[Omnibus GitLab documentation](https://gitlab.com/gitlab-org/omnibus-gitlab/tree/master/doc/settings/configuration.md).\n\n### Pre-configure Docker container\n\nYou can pre-configure the GitLab Docker image by adding the environment\nvariable `GITLAB_OMNIBUS_CONFIG` to docker run command. This variable can\ncontain any `gitlab.rb` setting and will be evaluated before loading the\ncontainer's `gitlab.rb` file. That way you can easily configure GitLab's\nexternal URL, make any database configuration or any other option from the\n[Omnibus GitLab template](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/files/gitlab-config-template/gitlab.rb.template).\n\n_Note: The settings contained in `GITLAB_OMNIBUS_CONFIG` will not be written to the `gitlab.rb` configuration file, they're evaluated on load._\n\nHere's an example that sets the external URL and enables LFS while starting\nthe container:\n\n```bash\ndocker run -d \\\n--hostname gitlab.example.com \\\n--env GITLAB_OMNIBUS_CONFIG=\"external_url 'http://my.domain.com/'; gitlab_rails['lfs_enabled'] = true;\" \\\n-p 443:443 -p 80:80 -p 22:22 \\\n--name gitlab \\\n--restart always \\\n-v /srv/gitlab/config:/etc/gitlab \\\n-v /srv/gitlab/logs:/var/log/gitlab \\\n-v /srv/gitlab/data:/var/opt/gitlab \\\nulm0/gitlab\n```\n\nNote that every time you execute a `docker run` command, you need to provide\nthe `GITLAB_OMNIBUS_CONFIG` option. The content of `GITLAB_OMNIBUS_CONFIG` is\n_not_ preserved between subsequent runs.\n\nThere are also a limited number of environment variables to configure GitLab.\nThey are documented in the [environment variables section of the GitLab documentation](https://docs.gitlab.com/ce/administration/environment_variables.html).\n\n## After starting a container\n\nAfter starting a container you can visit \u003chttp://localhost/\u003e or\n\u003chttp://192.168.59.103\u003e if you use boot2docker. It might take a while before\nthe Docker container starts to respond to queries.\n\nThe very first time you visit GitLab, you will be asked to set up the admin\npassword. After you change it, you can login with username `root` and the\npassword you set up.\n\n## Upgrade GitLab to newer version\n\nTo upgrade GitLab to a new version you have to:\n\n1. Stop the running container:\n\n    ```bash\n    docker stop gitlab\n    ```\n\n2. Remove existing container:\n\n    ```bash\n    docker rm gitlab\n    ```\n\n3. Pull the new image:\n\n    ```bash\n    docker pull ulm0/gitlab\n    ```\n\n4. Create the container once again with previously specified options:\n\n    ```bash\n    docker run -d \\\n    --hostname gitlab.example.com \\\n    -p 443:443 -p 80:80 -p 22:22 \\\n    --name gitlab \\\n    --restart always \\\n    -v /srv/gitlab/config:/etc/gitlab \\\n    -v /srv/gitlab/logs:/var/log/gitlab \\\n    -v /srv/gitlab/data:/var/opt/gitlab \\\n    ulm0/gitlab\n    ```\n\nOn the first run, GitLab will reconfigure and update itself.\n\n### Use tagged versions of GitLab\n\nWe provide tagged versions of GitLab Docker images.\n\nTo see all available tags check:\n\n- [GitLab tags](https://hub.docker.com/r/ulm0/gitlab/tags/)\n\nTo use a specific tagged version, replace `ulm0/gitlab` with\nthe GitLab version you want to run, for example `ulm0/gitlab:10.3.3`.\n\n### Run GitLab CE on public IP address\n\nYou can make Docker to use your IP address and forward all traffic to the\nGitLab CE container by modifying the `-p` flag.\n\nTo expose GitLab CE on IP 1.1.1.1:\n\n```bash\ndocker run -d \\\n--hostname gitlab.example.com \\\n-p 1.1.1.1:443:443 \\\n-p 1.1.1.1:80:80 \\\n-p 1.1.1.1:22:22 \\\n--name gitlab \\\n--restart always \\\n-v /srv/gitlab/config:/etc/gitlab \\\n-v /srv/gitlab/logs:/var/log/gitlab \\\n-v /srv/gitlab/data:/var/opt/gitlab \\\nulm0/gitlab\n```\n\nYou can then access your GitLab instance at `http://1.1.1.1/` and `https://1.1.1.1/`.\n\n### Expose GitLab on different ports\n\nGitLab will occupy by default the following ports inside the container:\n\n- `80` (HTTP)\n- `443` (if you configure HTTPS)\n- `8080` (used by Unicorn)\n- `22` (used by the SSH daemon)\n\n\u003e **Note:**\nThe format for publishing ports is `hostPort:containerPort`. Read more in\nDocker's documentation about [exposing incoming ports][docker-ports].\n\n\u003e **Warning:**\nDo NOT use port `8080` otherwise there will be conflicts. This port is already\nused by Unicorn that runs internally in the container.\n\nIf you want to use a different port than `80` (HTTP) or `443` (HTTPS) for the\ncontainer, you need to add a separate `-p` directive to the `docker run`\ncommand.\n\nFor example, to expose the web interface on port `8929`, and the SSH service on\nport `2289`, use the following `docker run` command:\n\n```bash\ndocker run -d \\\n--hostname gitlab.example.com \\\n-p 8929:80 -p 2289:22 \\\n--name gitlab \\\n--restart always \\\n-v /srv/gitlab/config:/etc/gitlab \\\n-v /srv/gitlab/logs:/var/log/gitlab \\\n-v /srv/gitlab/data:/var/opt/gitlab \\\nulm0/gitlab\n```\n\nYou then need to appropriately configure `gitlab.rb`:\n\n1. Set `external_url`:\n\n    ```sh\n    # For HTTP\n    external_url \"http://gitlab.example.com:8929\"\n\n    or\n\n    # For HTTPS (notice the https)\n    external_url \"https://gitlab.example.com:8929\"\n    ```\n\n    For more information see the [NGINX documentation](https://gitlab.com/gitlab-org/omnibus-gitlab/tree/master/doc/settings/nginx.md).\n\n2. Set `gitlab_shell_ssh_port`:\n\n    ```rb\n    gitlab_rails['gitlab_shell_ssh_port'] = 2289\n    ```\n\nFollowing the above example you will be able to reach GitLab from your\nweb browser under `\u003chostIP\u003e:8929` and push using SSH under the port `2289`.\n\nA `docker-compose.yml` example that uses different ports can be found in the\n[docker-compose](#install-gitlab-using-docker-compose) section.\n\n## Diagnose potential problems\n\nRead container logs:\n\n```bash\ndocker logs gitlab\n```\n\nEnter running container:\n\n```bash\ndocker exec -it gitlab /bin/bash\n```\n\nFrom within the container you can administer the GitLab container as you would\nnormally administer an\n[Omnibus installation](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/README.md)\n\n## Install GitLab using docker-compose\n\nWith [Docker compose] you can easily configure, install, and upgrade your\nDocker-based GitLab installation.\n\n1. [Install][install-compose] Docker Compose\n1. Create a `docker-compose.yml` file (or [download an example][down-yml]):\n\n    ```yaml\n    web:\n      image: 'ulm0/gitlab'\n      restart: always\n      hostname: 'gitlab.example.com'\n      environment:\n        GITLAB_OMNIBUS_CONFIG: |\n          external_url 'https://gitlab.example.com'\n          # Add any other gitlab.rb configuration here, each on its own line\n      ports:\n        - '80:80'\n        - '443:443'\n        - '22:22'\n      volumes:\n        - '/srv/gitlab/config:/etc/gitlab'\n        - '/srv/gitlab/logs:/var/log/gitlab'\n        - '/srv/gitlab/data:/var/opt/gitlab'\n    ```\n\n1. Make sure you are in the same directory as `docker-compose.yml` and run\n  `docker-compose up -d` to start GitLab\n\nRead [\"Pre-configure Docker container\"](#pre-configure-docker-container) to see\nhow the `GITLAB_OMNIBUS_CONFIG` variable works.\n\nBelow is another `docker-compose.yml` example with GitLab running on a custom\nHTTP and SSH port. Notice how the `GITLAB_OMNIBUS_CONFIG` variables match the\n`ports` section:\n\n```yaml\nweb:\n  image: 'ulm0/gitlab'\n  restart: always\n  hostname: 'gitlab.example.com'\n  environment:\n    GITLAB_OMNIBUS_CONFIG: |\n      external_url 'http://gitlab.example.com:9090'\n      gitlab_rails['gitlab_shell_ssh_port'] = 2224\n  ports:\n    - '9090:9090'\n    - '2224:22'\n  volumes:\n    - '/srv/gitlab/config:/etc/gitlab'\n    - '/srv/gitlab/logs:/var/log/gitlab'\n    - '/srv/gitlab/data:/var/opt/gitlab'\n```\n\nThis is the same as using `-p 9090:9090 -p 2224:22`.\n\n## Update GitLab using Docker compose\n\nProvided you [installed GitLab using docker-compose](#install-gitlab-using-docker-compose),\nall you have to do is run `docker-compose pull` and `docker-compose up -d` to\ndownload a new release and upgrade your GitLab instance.\n\n## Install GitLab into a cluster\n\nThe GitLab Docker images can also be deployed to various container scheduling platforms.\n\n* Kubernetes using the [GitLab Helm Charts](https://docs.gitlab.com/ce/install/kubernetes/).\n* Docker Cloud using the [docker-compose config](#install-gitlab-using-docker-compose).\n\n\u003c!-- - Mesosphere DC/OS using the [DC/OS Package](https://github.com/dcos/examples/tree/master/gitlab/1.8). --\u003e\n\n## Troubleshooting\n\n### Sysctl tunning\n\nRunning the image on a Raspbery Pi 3 or any other ARM board might require some `sysctl` values in order for it to run properly and have a good performance.\n\nAll you need to is add the following at the end of `/etc/sysctl.conf`:\n\n```sh\nkernel.sem = 250 32000 32 262\nkernel.shmall = 1048575\nkernel.shmmax = 4294967295\nnet.core.somaxconn = 1024\n```\n\nIt can be done with `nano` or `vim` (e.g. `sudo nano /etc/sysctl.conf`).\n\nOnce that is done, these values need to loaded to the system, you can do so by running `cat /etc/sysctl.conf /etc/sysctl.d/*.conf  | sudo sysctl -e -p -` and the host will be ready to run the GitLab docker image.\n\n### 500 Internal Error\n\nWhen updating the Docker image you may encounter an issue where all paths\ndisplay the infamous **500** page. If this occurs, try to run\n`docker restart gitlab` to restart the container and rectify the issue.\n\n### Permission problems\n\nWhen updating from older GitLab Docker images you might encounter permission\nproblems. This happens due to a fact that users in previous images were not\npreserved correctly. There's script that fixes permissions for all files.\n\nTo fix your container, simply execute `update-permissions` and restart the\ncontainer afterwards:\n\n```bash\ndocker exec gitlab update-permissions\ndocker restart gitlab\n```\n\n[docker compose]: https://docs.docker.com/compose/\n[install-compose]: https://docs.docker.com/compose/install/\n[down-yml]: docker/docker-compose.yml\n[docker-ports]: https://docs.docker.com/engine/reference/run/#/expose-incoming-ports\n\n### Linux ACL issues\n\nIf you are using file ACLs on the docker host, the `docker`[^1] group requires full access to the volumes in order for GitLab to work.\n\n```bash\n$ getfacl /srv/gitlab\n# file: /srv/gitlab\n# owner: XXXX\n# group: XXXX\nuser::rwx\ngroup::rwx\ngroup:docker:rwx\nmask::rwx\ndefault:user::rwx\ndefault:group::rwx\ndefault:group:docker:rwx\ndefault:mask::rwx\ndefault:other::r-x\n```\n\nIf these are not correct, set them with:\n\n```sh\n$ sudo setfacl -mR default:group:docker:rwx /srv/gitlab\n```\n\n[^1]: `docker` is the default group, if you've changed this, update your commands accordingly.\n\n### Getting help\n\nIf your problem is not listed here please see [getting help](https://about.gitlab.com/getting-help/) for the support channels.\n\nThese docker images are not officially supported by GitLab Inc. still efforts are made to keep them up to date.","funding_links":[],"categories":[],"sub_categories":[],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fulm0%2Fgitlab","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fulm0%2Fgitlab","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fulm0%2Fgitlab/lists"}