Skip to content
Snippets Groups Projects
Select Git revision
  • 13-4-stable protected
  • 13-3-stable protected
  • 5509-default-fresh-installs-to-pg12
  • 4160-better-wait-for-postgres-routine
  • patch-10
  • master default protected
  • pg-cert-update-docs
  • 5725-pgbouncer-should-support-multiple-authentication-options
  • rs-ci-sections
  • ignore-js-cache-dirs
  • 5728-qa-tests-failing-after-group-was-explicitly-set-for-repositories_storages
  • add-img-resizing-configs
  • deps/5a89a91-3b3d888
  • allow-setting-gitaly-git-bin-path
  • rename-piwik-to-matomo
  • docs-update-redirects-omnibus
  • 5665-allow-non-default-pg-port
  • ashmckenzie/gitlab-shell-ssl-cert-dir-support
  • eread/use-latest-docs-linting-image
  • if-forti_authenticator
  • 17.6.4+ee.0 protected
  • 17.6.4+ce.0 protected
  • 17.7.3+ee.0 protected
  • 17.7.3+ce.0 protected
  • 17.8.1+ee.0 protected
  • 17.8.1+ce.0 protected
  • 17.8.0+ee.0 protected
  • 17.8.0+ce.0 protected
  • 17.7.2+ee.0 protected
  • 17.7.2+ce.0 protected
  • 17.8.0+rc42.ee.0 protected
  • 17.8.0+rc42.ce.0 protected
  • 17.5.5+ee.0 protected
  • 17.5.5+ce.0 protected
  • 17.6.3+ee.0 protected
  • 17.6.3+ce.0 protected
  • 17.7.1+ee.0 protected
  • 17.7.1+ce.0 protected
  • 17.7.0+ee.0 protected
  • 17.7.0+ce.0 protected
40 results

README.md

Blame
  • Code owners
    Assign users and groups as approvers for specific file changes. Learn more.
    stage: Enablement
    group: Distribution
    info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers

    Building omnibus-gitlab packages and Docker images locally

    NOTE: Note: If you are a GitLab team member, you have access to our CI infrastructure which can be used to build these artifacts. Check the documentation for more details.

    omnibus-gitlab packages

    omnibus-gitlab uses the omnibus tool for building packages for the supported operating systems. The omnibus tool will detect the OS where it is being used and build packages for that OS. It is recommended to use a Docker container corresponding to the OS as the environment for building packages.

    How to build a custom package locally is described in the dedicated document.

    All-in-one Docker image

    NOTE: Note: If you want individual Docker images for each GitLab component instead of the all-in-one monolithic one, check out the CNG repository.

    GitLab's all-in-one Docker image uses the omnibus-gitlab package built for Ubuntu 16.04 under the hood. The Dockerfile is optimized to be used in a CI environment, with the expectation of packages being available over the Internet.

    We're looking at improving this situation in issue #5550.

    How to build an all-in-one Docker image locally is described in the dedicated document.