GITLAB setup on docker running for more than 21 hours, still running

:hugs: Please help fill in this template with all the details to help others help you more efficiently. Use formatting blocks for code, config, logs and ensure to remove sensitive data.

Problem to solve

Describe your question in as much detail as possible:

  • What are you seeing, and how does that differ from what you expect to see?
  • Consider including screenshots, error messages, and/or other helpful visuals

Steps to reproduce

Which troubleshooting steps have you already taken? Can you link to any docs or other resources so we know where you have been?

Configuration

Provide screenshots from the GitLab UI showing relevant configuration, if applicable.
On self-managed instances, add the relevant configuration settings or changes.

Versions

Please select whether options apply, and add the version information.

Versions

Helpful resources

  1. Before opening a new topic, make sure to search for keywords in the forum search
  2. Check the GitLab project for existing issues. If you encounter a bug, please create a bug report issue.
  3. Troubleshooting docs: Self-managed GitLab instances.

Thanks for taking the time to be thorough in your request, it really helps! :blush:

sudo docker run --detach
–hostname gitlab.example.com
–env GITLAB_OMNIBUS_CONFIG=“external_url ‘http://gitlab.example.com’”
–publish 443:443 --publish 80:80 --publish 22:22
–name gitlab
–restart always
–volume $GITLAB_HOME/config:/etc/gitlab
–volume $GITLAB_HOME/logs:/var/log/gitlab
–volume $GITLAB_HOME/data:/var/opt/gitlab
–shm-size 256m
gitlab/gitlab-ee:-ee.0

This is taking more than 21 hours running GITLAB on docker. Still running. Is it usual, how long should i wait.

FYI, I have edited your post and removed the phone number.

Sorry, if it is not to be put here. I was looking for help with through text/phone. By any change you know why it took more than a day and still running without any errors though?

We remove personal credentials and data which can be abused by spammers or otherwise malicious actors.

This forum is a community forum where GitLab community members help each other. If you are looking for Enterprise support options that include phone support and/or faster help, I’d recommend getting an Enterprise subscription. Pricing | GitLab

I don’t fully understand the error and question. The docker command detaches the container startup into the background, so the container will continue to run, as can be seen with docker ps. What’s the error you are seeing specifically to GitLab not working?

No problem for removing the phone number.

I am following procedure mentioned in this link Install GitLab by using Docker | GitLab

AT the pint where the docker run command is run, it is showing the processing happening in the logs continuously without any errors.

However when I try that external link that we passed to the docker run command as here --env GITLAB_OMNIBUS_CONFIG=“external_url ‘http://gitlab.example.com’”

This link http;//gitlan.example.com gives 404 error indicating that preprocessing is not complete.

I am waiting till I see no scrolling in the logs since yesterday but it never stops.

Please help. There is an urgency to do a PoC ASAP.

Thanks for your help.

Regards,
Ravindra

PS:- I was trying the correct url only, there is a typo above.

Now i am just noticing an error:

2024-07-26 19:31:36 {“error”:“keywatcher: pubsub receive: EOF”,“level”:“error”,“msg”:“”,“time”:“2024-07-26T14:01:36Z”}

What is the way to move forward. I didn’t want to quit after waiting so long to have it working perfectly.

============= and the below lines keeps repeating all the time.=====

2024-07-26 19:31:36

2024-07-26 19:31:36 ==> /var/log/gitlab/gitlab-workhorse/current <==

2024-07-26 19:31:36 {“error”:“keywatcher: pubsub receive: EOF”,“level”:“error”,“msg”:“”,“time”:“2024-07-26T14:01:36Z”}

2024-07-26 19:31:36 {“address”:“/var/opt/gitlab/redis/redis.socket”,“level”:“info”,“msg”:“redis: dialing”,“network”:“unix”,“time”:“2024-07-26T14:01:36Z”}

2024-07-26 19:31:39

2024-07-26 19:31:39 ==> /var/log/gitlab/gitlab-exporter/current <==

2024-07-26 19:31:39 2024-07-26_14:01:39.28515 ::1 - - [26/Jul/2024:14:01:39 UTC] “GET /sidekiq HTTP/1.1” 200 131923

2024-07-26 19:31:39 2024-07-26_14:01:39.28540 - → /sidekiq

2024-07-26 19:31:43 2024-07-26_14:01:43.10596 ::1 - - [26/Jul/2024:14:01:43 UTC] “GET /ruby HTTP/1.1” 200 1082

2024-07-26 19:31:43 2024-07-26_14:01:43.10622 - → /ruby

2024-07-26 19:31:44 2024-07-26_14:01:44.14219 ::1 - - [26/Jul/2024:14:01:44 UTC] “GET /database HTTP/1.1” 200 2430

2024-07-26 19:31:44 2024-07-26_14:01:44.14242 - → /database

http://gitlab.example.com/

Is an example in the documentation for a GitLab instance URL. You need to replace it with a working FQDN in your network. For example, the DNS entry resolves to the VM host IP address where the Docker container is running on, listening on port http/80 and https/443.

It gets put in the docker container’s /etc/hosts and with an ip addresses assigned.

So when i ping gitlab.example.com it solves to 172.17.0.3

And since it a implicit network type “bridge”

I have put this hostname in the /etc/hosts of the MAC host also as 127.0.0.1

So it is resolving.from the host as well.

I have been working on this kind of set for other products and it works.

Regards,
Ravindra

ping sends ICMP packets, I’d suggest trying curl or other http testing tools instead.

The GitLab instance log verbosity can also be increased. Logs on Linux package installations | GitLab

Maybe it is a resource issue on the Docker host. How much CPU, RAM, disk storage are available?

I’d also recommend reviewing the steps in

I can try again assuming, the present setup has failed.

But can you give me an idea how long it should take. It should be hours right?

Regards,
Ravindra