sameersbn / sameersbn/docker-gitlab
Error at container startup sed: couldn't open temporary file /home/git/gitlab/config...
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
When I start this container I have an error that disappear at restart
gitlab_1_dabd7146875a | Installing configuration templates...
gitlab_1_dabd7146875a | SSL key and certificates for Registry were not found
gitlab_1_dabd7146875a | Assuming that the Registry is running behind a HTTPS enabled load balancer.
gitlab_1_dabd7146875a | Configuring gitlab...
gitlab_1_dabd7146875a | Configuring gitlab::database
gitlab_1_dabd7146875a | sed: couldn't open temporary file /home/git/gitlab/config/sednyAaZK: Permission denied
Can you give me some advice on how to fix it ?
I read its becouse i not have
USERMAP_UID AND USERMAP_GID
but after change this from default 1000 to 1010 i have not URL to go and not work all time.
This is my config yml:
gitlab:
environment:
DEBUG: 'false'
GITLAB_PORT: 10083
GITLAB_SECRETS_DB_KEY_BASE: qcs-gitlab-app
GITLAB_SECRETS_OTP_KEY_BASE: qcs-gitlab-app
GITLAB_SECRETS_SECRET_KEY_BASE: qcs-gitlab-app
GITLAB_SSH_PORT: 10022
image: sameersbn/gitlab:11.4.0
links:
- redis:redisio
- postgresql:postgresql
ports:
- 10083:80
- '10022:22'
restart: always
postgresql:
environment:
DB_EXTENSION: pg_trgm
DB_NAME: gitlabhq_production
DB_PASS: password
DB_USER: gitlab
image: sameersbn/postgresql:9.6-2
restart: always
redis:
command:
- --loglevel warning
image: sameersbn/redis:latest
restart: always
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the container startup log and the supplied config.yml, focusing on the /home/git/gitlab/config path and the USERMAP_UID and USERMAP_GID settings. Reproduce the startup sequence and determine why sed cannot create its temporary file; done means the container starts reliably without the permission error and remains reachable at the configured URL.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100