sameersbn / docker-gitlab

Dockerized GitLab
http://www.damagehead.com/docker-gitlab/
MIT License
7.9k stars 2.14k forks source link

Fail to create Backup & restore #1642

Open m4jid-ha opened 6 years ago

m4jid-ha commented 6 years ago

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

Scukerman commented 6 years ago

Obviously you need to run executable file with arguments: $ /sbin/entrypoint.sh app:rake gitlab:backup:restore

mikew commented 6 years ago

@Scukerman docker-compose run ... respects the containers ENTRYPOINT, which is already set to /sbin/entrypoint.sh. Note that even the project's own documentation doesn't mention /sbin/entrypoint.sh: https://github.com/sameersbn/docker-gitlab#creating-backups

@majidhashemi70 does your docker-compose.yml file override the entrypoint?

stale[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had any activity for the last 60 days. It will be closed if no further activity occurs during the next 7 days. Thank you for your contributions.