sameersbn / sameersbn/docker-gitlab

Fail to create Backup & restore

Open
#1,642 3 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

wontfix
Dominant language
Shell
Stars
8.1k
Forks
2.1k
Avg merge
17h 47m
Merged PRs (30d)
7

Description

Hi every body
i use the docker-compose.yml file but i change the gitlab image's from sameersbn/gitlab:10.8.3-1 to gitlab/gitlab-ce:10.0.5-ce.0 . i pull my costume image from docker hub to my docker repository and when i run docker-compose up command , Redis & Postgresql & Gitlab well be create and i access to my gitlab by ip address 127.0.0.1:10080 . but then i want to create backup with "docker-compose run --rm gitlab app:rake gitlab:backup:create" command and restore with "docker-compose run --rm gitlab app:rake gitlab:backup:restore " command in both command shown this error:

[root@devops git15]# docker-compose run --rm gitlab app:rake gitlab:backup:create
Starting git15_redis_1 ... done
Starting git15_postgresql_1 ... done
Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: "app:rake": executable file not found in $PATH": unknown
[root@devops git15]# docker-compose run --rm gitlab app:rake gitlab:backup:restore
Starting git15_redis_1 ... done
Starting git15_postgresql_1 ... done
Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: "app:rake": executable file not found in $PATH": unknown

tnx for any help

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with docker-compose.yml and the selected GitLab image, then inspect how its entrypoint handles the app:rake backup commands. Reproduce the reported docker-compose run commands and determine whether backup and restore work with the configured image; done means the compatible command or configuration is identified and documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose, shell
Domain
devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.