[go: up one dir, main page]

Skip to content

Custom/Global GIT Hooks should be available in the Docker image even after restart or update/upgrade

Problem to solve

GIT Hooks should remain within the Docker container after rebuild/upgrade.

Intended users

All users who install Gitlab through the official Docker image.

Further details

Right now you have to copy your Hooks manually to the folder /opt/gitlab/embedded/service/gitlab-shell/hooks/. This is pretty uncomfortable especially if you need to check all the time if the Hooks still exist.

Proposal

As a developer/DevOp/Sysadmin I would like to install Gitlab through the existing Docker images but those images should contain a so called VOLUME directive. So we can mount our global hooks automatically to the correct position within the image. E.g.: /opt/gitlab/embedded/service/gitlab-shell/hooks/pre-receive.d/my-custom-hook.sh The hook should automatically be owned by the git user and have executable permissions.

Permissions and Security

It's just adding a VOLUME to the docker image.

Documentation

It's just adding a VOLUME to the docker image.

Testing

It's just adding a VOLUME to the docker image.

What does success look like, and how can we measure that?

It's just adding a VOLUME to the docker image.

What is the type of buyer?

Should be available in the community edition (Core)

Links / references

https://docs.docker.com/engine/reference/builder/#volume

Edited by 🤖 GitLab Bot 🤖