---
title: "Discussion on \"Gitlab runner and Docker compose trap\" | Hashnode"
description: "Discussion on \"Gitlab runner and Docker compose trap\". Learn why GitLab Runner config disappears when moving to Docker Compose. This guide explains Docker volume prefixes and how to ensure persistent storage."
url: "https://hashnode.com/posts/gitlab-runner-and-docker-compose-trap/697b421097fa96d4947ea3f7"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Gitlab runner and Docker compose trap](https://manhhanguyen.work/gitlab-runner-and-docker-compose-trap?utm_source=hashnode&utm_medium=feed)

Learn why GitLab Runner config disappears when moving to Docker Compose. This guide explains Docker volume prefixes and how to ensure persistent storage.

Jan 29 · 5 min read · manhhanguyen.work  
Read the article

-   [#docker](https://hashnode.com/tag/docker)
-   [#gitlab-ci](https://hashnode.com/tag/gitlab-ci)
-   [#gitlab-runner](https://hashnode.com/tag/gitlab-runner)
-   [#docker-compose](https://hashnode.com/tag/docker-compose)
-   [#devops](https://hashnode.com/tag/devops)
-   [#troubleshooting](https://hashnode.com/tag/troubleshooting)
-   [#debugging](https://hashnode.com/tag/debugging)
-   [#linux](https://hashnode.com/tag/linux)

## Written by

[Nguyen Manh Ha](https://hashnode.com/@Hanm)

@Hanm

  
[View profile](https://hashnode.com/@Hanm)

C++, Python, Swift, Linux, security

## Responses

Markdown supported · ⌘↵ to post

No responses yet.