Does anyone has a running/working instance of that docker? 

9 minutes ago, Jaster said:

Does anyone has a running/working instance of that docker? 

I have mine up and running. There's a bunch of configuration you have to do to get it to work with Gitlab. This is a good start

https://docs.gitlab.com/ee/integration/sourcegraph.html#enable-the-sourcegraph-feature-flag

 

It's a bit tricky with a lot of configurations. Let me know if you run into problems and I'll be happy to show you what I did.

1 minute ago, frakman1 said:

I have mine up and running. There's a bunch of configuration you have to do to get it to work with Gitlab. This is a good start

https://docs.gitlab.com/ee/integration/sourcegraph.html#enable-the-sourcegraph-feature-flag

 

It's a bit tricky with a lot of configurations. Let me know if you run into problems and I'll be happy to show you what I did.

I'm not even talking about sourcegraph. the gitlab container "died" after one of the latest updates. It does come up, but no way to connect to it.

The log give some panic errors:

 

8 minutes ago, Jaster said:

I'm not even talking about sourcegraph. the gitlab container "died" after one of the latest updates. It does come up, but no way to connect to it.

Oh sorry for the misunderstanding. What version of Gitlab is it? I'll try upgrading mine to the latest and test it out.

2 hours ago, frakman1 said:

Oh sorry for the misunderstanding. What version of Gitlab is it? I'll try upgrading mine to the latest and test it out.

Latest gitlab-ce. Posted my config a few posts above.

On 11/26/2018 at 6:06 AM, ElectricBadger said:

I've got this in my nginx config (in proxy-confs/gitlab-ce.subdomain.conf):

server {
  listen *:80;
  server_name  registry.subdomain.duckdns.org;
  server_tokens off;
  return 301 https://$http_host:$request_uri;
  access_log  /config/log/nginx/gitlab_registry_access.log;
  error_log   /config/log/nginx/gitlab_registry_error.log;
}

server {
  listen *:443 ssl;
  server_name  registry.subdomain.duckdns.org;
  server_tokens off;

  include /config/nginx/ssl.conf;
  client_max_body_size 0;
  chunked_transfer_encoding on;

  access_log  /config/log/nginx/gitlab_registry_access.log;
  error_log   /config/log/nginx/gitlab_registry_error.log;

  location / {
    include /config/nginx/proxy.conf;
    proxy_pass http://gitlab:9381;
  }

  location /v2/ {
    include /config/nginx/proxy.conf;
    add_header 'Docker-Distribution-Api-Version' 'registry/2.0' always;
    proxy_pass http://gitlab:9381;
  }
}

and this as the container's extra parameters (minus setup for email, backups and container registry):

--env GITLAB_OMNIBUS_CONFIG="external_url 'https://git.subdomain.duckdns.org';registry_external_url 'https://registry.subdomain.duckdns.org';gitlab_rails['gitlab_ssh_host']='git.subdomain.duckdns.org';nginx['listen_port']=9080;nginx['listen_https']=false;nginx['hsts_max_age']=0;registry_nginx['listen_port']=9381;registry_nginx['listen_https']=false;registry_nginx['enable']=true;registry['enable']=true;"

If you want to use ssh rather than https for cloning/pushing, you'll need to add a port to the container for it: host port 9022 (or whatever you like that isn't being used), container port 22. I then add this in ~/.ssh/config:

Host gitlab
HostName git.subdomain.duckdns.org
Port 9022
User gitlab

although I have to say that, while this works for Mac and Linux/BSD, I have no idea what the equivalent is for Windows!

If possible, will you expand on this for me? I wrote off SSH over the internet for this Gitlab-CE container, but I would really like to use it and provide this service in a responsible way. I want to do this through the let's encrypt proxy.

Where in the proxy-confs/gitlab-ce.subdomain.conf is port 9022 dealt with? If I forward 22 from my router to the unRAID host's 9022, why is configuring the letsencrypt proxy involved?

Also, thank you for posting your configs.

3 hours ago, codecitymayor said:

If possible, will you expand on this for me? I wrote off SSH over the internet for this Gitlab-CE container, but I would really like to use it and provide this service in a responsible way. I want to do this through the let's encrypt proxy.

Where in the proxy-confs/gitlab-ce.subdomain.conf is port 9022 dealt with? If I forward 22 from my router to the unRAID host's 9022, why is configuring the letsencrypt proxy involved?

Also, thank you for posting your configs.

The letsencrypt proxy only handles HTTPS, not SSH — I think I posted that to show what I was doing to get HTTPS working, but it's been a while since I did that

 

Forwarding the port should be all you need to do for SSH, but I decided not to bother with SSH in the end, and just use HTTPS. I can't offer much more help at the moment as my container doesn't seem to want to come up after the last auto-update…

9 hours ago, ElectricBadger said:

I can't offer much more help at the moment as my container doesn't seem to want to come up after the last auto-update…

@ElectricBadger @JasterCan you go back to a working earlier version? I have mine pinned to 12.5.2-ce.0 which I know works for me. I don't update the docker but when I do, I pin it to the version I want. See screenshot below for my Docker Settings

 

12 hours ago, frakman1 said:

@ElectricBadger @JasterCan you go back to a working earlier version? I have mine pinned to 12.5.2-ce.0 which I know works for me. I don't update the docker but when I do, I pin it to the version I want. See screenshot below for my Docker Settings

 

How do I go back to a specific version?...

1 hour ago, Jaster said:

How do I go back to a specific version?...

In my screenshot above I show the string I used for "Repository". This allows you to select the tagged versionof Gitlab that you want.

 

Change it from:

gitlab/gitlab-ce:latest

to :

gitlab/gitlab-ce:12.5.2-ce.0

(or anything you want)

 

You can go to dockerhub and choose from a list of official tags. 

On 12/17/2019 at 10:02 AM, Jaster said:

Does anyone has a running/working instance of that docker? 

I just updated mine to the latest 12.5.2 and it works fine:

 

 

I've noticed that on some docker containers that keep crashing sometimes, that if I edit the Docker configuration and just add an empty field or make a trivial change to the description and Apply it, then it re-runs the docker command to create the container and it starts working again. Even with a pinned version of the image so it can't be because of a new feature or bug-fix. Try doing that.

I tried several version and also adding/removing some settings. The container just won't come up.

 

I assume something happened during a major version change... or I have something wrong inside the git lab config...?

Edited December 21, 20196 yr by Jaster

Hi guys,

 

I got a problem with my gitlab-ce docker, it cannot start anymore. I use the latest version.

If someone can help me, it well be appreciate.

 

 

 

 

It appears to be permission issues against what is presumably your appdata share for GitLab.  Have you inadvertently run the new permissions tool against that share?

 

Do you have any other problems with the server / shares?

 

What's you docker run command look like?

Thanks Squid, yes I think I have run the new permissions tool on appdata, it's a mistake. At this moment I don't think I have other problem, but I will find out pready soon.

 

About the "docker run command", I want to show you but I don't know where I can find that, could you tell my more about that.

 

 

Thank you

44 minutes ago, corso said:

yes I think I have run the new permissions tool on appdata, it's a mistake.

Yup.  That's the reason why the Fix Common Problems plugin has also on the Tools Page a "Docker Safe" permissions tool which specifically excludes the appdata share.

 

Trouble here is that any given docker app may have its own arbitrary permission and ownership requirements within it's appdata.  Generally it's just plain easier to delete the entire folder in question and start over than try and figure out what it's requirements may be.

 

But, in a pinch this command *may* work in a last resort (it can't get any worse  )

 

chmod 0777 -R /mnt/cache/appdata/gitlab-ce

 

@Squid I have already tested to give all access to the folder with this command, the docker want start. [emoji45]

Envoyé de mon SM-G965W en utilisant Tapatalk

@Squid, I resolved my problem using WinSCP and changing the permissions on appdata/gitlab-ce to 0777 (I have check "Set group, owner and permissions recursively"), I don't understand why it didn't work with "putty" the first time... Thanks

When I try to run this container it consumes almost everything of my cpu, even though it's pinned to 4 threads.

Unusable for me

 

FYI: my cpu has 48 threads so it's not that it's a low grade cpu...

Edited February 4, 20206 yr by WEHA
FYI

In Fix Common Problems, I keep getting the following Warnings, I tried the fixes available for both, but it continues to show. Does anyone else get this?

Quote

WARNINGS FOUND    SUGGESTED FIX    
Template URL for docker application GitLab-CE is not the as what the template author specified.    The template URL the author specified is https://raw.githubusercontent.com/malvarez00/unRAID-Docker-Templates/master/malvarez00/GitLab-CE.xml. The template can be updated automatically with the correct URL.     
Template URL for docker application GitLab-CE is not the as what the template author specified.    The template URL the author specified is https://raw.githubusercontent.com/frakman1/docker-templates/master/tynor88/gitlab-ce.xml. The template can be updated automatically with the correct URL. 

 

4 hours ago, timethrow said:

In Fix Common Problems, I keep getting the following Warnings, I tried the fixes available for both, but it continues to show. Does anyone else get this?

 

Rescan in FCP.  It'll either disappear or you'll have to hit apply fix one more time

Hi what happened to the last update, 

After the update all work fine except when I want to access the individual file, the gitlab insert the internal port 9433 to the link and and the browser does not want to load the file, check it here for example:

https://git.devboard.tech/boot-loaders/fpga-risc-v

 

If you navigate the directories all OK, when you load file the issue appear.

So I've got this image running, but I'd like to be able to point my browser directly to it without having to specify the http(s) port. I've set the network to br0 with it's own IP address. I also changed all of the port numbers to their standard values (80, 443, 22). When I open the webgui from the unraid docker page, the url still goes to port 9080 and it works. But if I just enter the IP address without specifying a port, the connection is refused.

 

How come the image doesn't respect the port settings?

 

What else do I have to change?

 

7 hours ago, RichardRob said:

So I've got this image running, but I'd like to be able to point my browser directly to it without having to specify the http(s) port. I've set the network to br0 with it's own IP address. I also changed all of the port numbers to their standard values (80, 443, 22). When I open the webgui from the unraid docker page, the url still goes to port 9080 and it works. But if I just enter the IP address without specifying a port, the connection is refused.

 

How come the image doesn't respect the port settings?

 

What else do I have to change?

 

You only changed the port mappings. Gitlab itself doesn't know about those mappings.

When you set an IP for the container, the port mappings are obsolete and will be the ones set in the container (Which is the container ports in the template).  So to change these to the standard http/https/ssh ports, you need to change the settings file in gitlab.

On 3/16/2020 at 1:52 AM, saarg said:

So to change these to the standard http/https/ssh ports, you need to change the settings file in gitlab.

Is that the proxy-confs/gitlab-ce.subdomain.conf file which everyone mentions in this thread without ever providing a full path?