thomast_88

You are using the old template where the port mappins are using already reserved ports by unraid. E.g. port 80. (I made a mistake in the initial template) Can you try to delete the docker container, the template and the mounted volume folders? This is how you delete the template: unRAID Menu --> Docker --> Add Container --> Choose my-Gitlab-CE --> Click on the red cross in the top. After this is done, try to reinstall it and it should be running on port: 9080

Can you post a screenshot of how the docker is setup? I have made some modifications to the unRAID template so that it should startup withouth any needs to configure the gitlab.rb file.

Are you being serious ? They are not random characters it's the hostname of the container and as such you're being redirected to the hostname of the container which is the correct behaviour due to the default gitlab conf. 2 solutions -- 1 - As above modify gitlab.rb 2 - Set a static container hostname I didn't realise. I didn't have to change anything in the previous versions of this docker. It started when they pushed an update a couple of days ago.

^^^ This Bingo How is it working out for you? Are the url redirects also replaced with some random chars?

Post some logs.

Looks like mine. Other users experienced that error aswell. (https://gitlab.com/gitlab-org/omnibus-gitlab/issues/721) Could you try to delete the docker, wipe /mnt/cache/appdata/gitlab-ce and try to install it from stracth? Ok did what you suggested, but I get either "Site can't be reached" or it changes the IP address of my unRAID box to chars. Example: IP is 192.168.1.2 (Gitlab is point to port 45300), opening the webui it takes me to the site but then redirects to http://5a2ef303db9f/users/sign_in. Here's the log http://pastebin.com/L7p6N7Zg. It looks like its the SHA2 key (root@5a2ef303db9f). Any ideas? Use a direct link (like i suggested in a previous post). In Your case http://192.168.1.2:45300/users/sign_in I have yet to figure out why it's changing the ip address to these chars. It started on that 2 days ago when they pushed the last update. The direct link takes me to: http://5a2ef303db9f/users/password/edit?reset_password_token=3yaDdMTpS3DKxbydzfdJ. :o Whenever it inserts those magic chars just replace it with the correct IP/Port. Eventually it will work after all has been setup. Remember to use the root user for the intial login. I will try to figure out why the IP gets replaced with those chars. Nope, what do you mean by "setup"? After you have logged in with the root user, it will ask you to change the password. Once it's up and running it shouldn't mess with those URL redirects. I still haven't figured out why it does that - it seems it started after their last update.

Any plans to create another beta of the Nextcloud beta branch :-) ? Version 10: https://nextcloud.com/install/#testing

Looks like mine. Other users experienced that error aswell. (https://gitlab.com/gitlab-org/omnibus-gitlab/issues/721) Could you try to delete the docker, wipe /mnt/cache/appdata/gitlab-ce and try to install it from stracth? Ok did what you suggested, but I get either "Site can't be reached" or it changes the IP address of my unRAID box to chars. Example: IP is 192.168.1.2 (Gitlab is point to port 45300), opening the webui it takes me to the site but then redirects to http://5a2ef303db9f/users/sign_in. Here's the log http://pastebin.com/L7p6N7Zg. It looks like its the SHA2 key (root@5a2ef303db9f). Any ideas? Use a direct link (like i suggested in a previous post). In Your case http://192.168.1.2:45300/users/sign_in I have yet to figure out why it's changing the ip address to these chars. It started on that 2 days ago when they pushed the last update. The direct link takes me to: http://5a2ef303db9f/users/password/edit?reset_password_token=3yaDdMTpS3DKxbydzfdJ. :o Whenever it inserts those magic chars just replace it with the correct IP/Port. Eventually it will work after all has been setup. Remember to use the root user for the intial login. I will try to figure out why the IP gets replaced with those chars.

Looks like mine. Other users experienced that error aswell. (https://gitlab.com/gitlab-org/omnibus-gitlab/issues/721) Could you try to delete the docker, wipe /mnt/cache/appdata/gitlab-ce and try to install it from stracth? Ok did what you suggested, but I get either "Site can't be reached" or it changes the IP address of my unRAID box to chars. Example: IP is 192.168.1.2 (Gitlab is point to port 45300), opening the webui it takes me to the site but then redirects to http://5a2ef303db9f/users/sign_in. Here's the log http://pastebin.com/L7p6N7Zg. It looks like its the SHA2 key (root@5a2ef303db9f). Any ideas? Use a direct link (like i suggested in a previous post). In Your case http://192.168.1.2:45300/users/sign_in I have yet to figure out why it's changing the ip address to these chars. It started on that 2 days ago when they pushed the last update.

Looks like mine. Other users experienced that error aswell. (https://gitlab.com/gitlab-org/omnibus-gitlab/issues/721) Could you try to delete the docker, wipe /mnt/cache/appdata/gitlab-ce and try to install it from stracth?

And you're not using a user share e.g. /mnt/user/appdata rather than /mnt/cache/appdata for the application files?

You've got to give me something in order for me to help. What happens when you try to access the WebUI? Are you trying HTTP or HTTPS? - You should use http unless you've changed the config file to make https work Can you try with this direct link: http://[iP]:[PORT]/users/sign_in Post the output of the log on pastebin so we can see it

Can you post the docker run command which is being used or a screenshot of the docker configuration? Mine is working fine with this config: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="GitLab-CE" --net="bridge" -e TZ="Europe/Paris" -e HOST_OS="unRAID" -p 45300:80/tcp -p 45305:443/tcp -p 45310:22/tcp -v "/mnt/cache/appdata/gitlab-ce/config":"/etc/gitlab":rw -v "/mnt/cache/appdata/gitlab-ce/data":"/var/opt/gitlab":rw -v "/mnt/cache/appdata/gitlab-ce/log":"/var/log/gitlab":rw gitlab/gitlab-ce

Any progress on this? :-)

Which version of unRAID? Can you post a screenshot of your container configuration?

Does the same thing happen if you run the command in command line? Just go edit the container, remove the problem variable and hit save. Then you will have the docker run command in the last command box. Copy it and ssh into your server and issue the command with the added problem variable. If that works, use the full path from /usr/local/emhttp/etc... and see if that works. If not, it's a bug in dockerman. Ok i tried both things, this is the result: docker run (works fine): root@unRAID:/mnt/user/appdata# docker run -d --name="GitLab-CE" --net="bridge" -e TZ="Europe/Paris" -e HOST_OS="unRAID" -p 45300:80/tcp -p 45305:443/tcp -p 45310:22/tcp -v "/mnt/cache/appdata/gitlab-ce/config":"/etc/gitlab":rw -v "/mnt/cache/appdata/gitlab-ce/data":"/var/opt/gitlab":rw -v "/mnt/cache/appdata/gitlab-ce/log":"/var/log/gitlab":rw --env GITLAB_OMNIBUS_CONFIG="external_url 'http://my.domain.com/'; gitlab_rails['lfs_enabled'] = true;" gitlab/gitlab-ce 724e403bc962631a9aa773d24f8657055f6d18f6db854a38794916e4bcf7680e docker run full path (works fine): root@unRAID:/mnt/user/appdata# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="GitLab-CE" --net="bridge" -e TZ="Europe/Paris" -e HOST_OS="unRAID" -p 45300:80/tcp -p 45305:443/tcp -p 45310:22/tcp -v "/mnt/cache/appdata/gitlab-ce/config":"/etc/gitlab":rw -v "/mnt/cache/appdata/gitlab-ce/data":"/var/opt/gitlab":rw -v "/mnt/cache/appdata/gitlab-ce/log":"/var/log/gitlab":rw --env GITLAB_OMNIBUS_CONFIG="external_url 'http://my.domain.com/'; gitlab_rails['lfs_enabled'] = true;" gitlab/gitlab-ce 7b3c680e8609383b4d28d9f134d4735c162acfd6a1811e5ca0dcbe5ba8c9604b So it must be something in the WebUI i suppose? Looks like a webgui bug then. You should file a defect report so it gets picked up. I'm confused who this should be filed to. The unRAID team or Squid (creator of CA) ? It's not CA. So go to the defect reports board and read the sticky on how to report a defect and then make the defect report accordingly. Ok thanks for the help. For reference i filed in a defect report about this bug: https://lime-technology.com/forum/index.php?topic=50385.0

Does the same thing happen if you run the command in command line? Just go edit the container, remove the problem variable and hit save. Then you will have the docker run command in the last command box. Copy it and ssh into your server and issue the command with the added problem variable. If that works, use the full path from /usr/local/emhttp/etc... and see if that works. If not, it's a bug in dockerman. Ok i tried both things, this is the result: docker run (works fine): root@unRAID:/mnt/user/appdata# docker run -d --name="GitLab-CE" --net="bridge" -e TZ="Europe/Paris" -e HOST_OS="unRAID" -p 45300:80/tcp -p 45305:443/tcp -p 45310:22/tcp -v "/mnt/cache/appdata/gitlab-ce/config":"/etc/gitlab":rw -v "/mnt/cache/appdata/gitlab-ce/data":"/var/opt/gitlab":rw -v "/mnt/cache/appdata/gitlab-ce/log":"/var/log/gitlab":rw --env GITLAB_OMNIBUS_CONFIG="external_url 'http://my.domain.com/'; gitlab_rails['lfs_enabled'] = true;" gitlab/gitlab-ce 724e403bc962631a9aa773d24f8657055f6d18f6db854a38794916e4bcf7680e docker run full path (works fine): root@unRAID:/mnt/user/appdata# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="GitLab-CE" --net="bridge" -e TZ="Europe/Paris" -e HOST_OS="unRAID" -p 45300:80/tcp -p 45305:443/tcp -p 45310:22/tcp -v "/mnt/cache/appdata/gitlab-ce/config":"/etc/gitlab":rw -v "/mnt/cache/appdata/gitlab-ce/data":"/var/opt/gitlab":rw -v "/mnt/cache/appdata/gitlab-ce/log":"/var/log/gitlab":rw --env GITLAB_OMNIBUS_CONFIG="external_url 'http://my.domain.com/'; gitlab_rails['lfs_enabled'] = true;" gitlab/gitlab-ce 7b3c680e8609383b4d28d9f134d4735c162acfd6a1811e5ca0dcbe5ba8c9604b So it must be something in the WebUI i suppose? Looks like a webgui bug then. You should file a defect report so it gets picked up. I'm confused who this should be filed to. The unRAID team or Squid (creator of CA) ?

Does the same thing happen if you run the command in command line? Just go edit the container, remove the problem variable and hit save. Then you will have the docker run command in the last command box. Copy it and ssh into your server and issue the command with the added problem variable. If that works, use the full path from /usr/local/emhttp/etc... and see if that works. If not, it's a bug in dockerman. Ok i tried both things, this is the result: docker run (works fine): root@unRAID:/mnt/user/appdata# docker run -d --name="GitLab-CE" --net="bridge" -e TZ="Europe/Paris" -e HOST_OS="unRAID" -p 45300:80/tcp -p 45305:443/tcp -p 45310:22/tcp -v "/mnt/cache/appdata/gitlab-ce/config":"/etc/gitlab":rw -v "/mnt/cache/appdata/gitlab-ce/data":"/var/opt/gitlab":rw -v "/mnt/cache/appdata/gitlab-ce/log":"/var/log/gitlab":rw --env GITLAB_OMNIBUS_CONFIG="external_url 'http://my.domain.com/'; gitlab_rails['lfs_enabled'] = true;" gitlab/gitlab-ce 724e403bc962631a9aa773d24f8657055f6d18f6db854a38794916e4bcf7680e docker run full path (works fine): root@unRAID:/mnt/user/appdata# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="GitLab-CE" --net="bridge" -e TZ="Europe/Paris" -e HOST_OS="unRAID" -p 45300:80/tcp -p 45305:443/tcp -p 45310:22/tcp -v "/mnt/cache/appdata/gitlab-ce/config":"/etc/gitlab":rw -v "/mnt/cache/appdata/gitlab-ce/data":"/var/opt/gitlab":rw -v "/mnt/cache/appdata/gitlab-ce/log":"/var/log/gitlab":rw --env GITLAB_OMNIBUS_CONFIG="external_url 'http://my.domain.com/'; gitlab_rails['lfs_enabled'] = true;" gitlab/gitlab-ce 7b3c680e8609383b4d28d9f134d4735c162acfd6a1811e5ca0dcbe5ba8c9604b So it must be something in the WebUI i suppose?

Hi I'm trying to pass in a variable which contains a ';' in the value (it's a convention when using the official GitLab docker and you want to change some configuration key/value pairs: http://docs.gitlab.com/omnibus/docker/) However i encounter an issue as soon as i click "Add Container" or try to update the container with this particular variable. Variable name: GITLAB_OMNIBUS_CONFIG Variable value: external_url 'http://my.domain.com/'; gitlab_rails['lfs_enabled'] = true; I also tried adding it directly into the "Extra Parameters" like this: --env GITLAB_OMNIBUS_CONFIG="external_url 'http://my.domain.com/'; gitlab_rails['lfs_enabled'] = true;" but i still get the same error: The command failed. sh: /usr/local/emhttp: Is a directory Attached some screenshots as well

GitLab Community Edition docker image based on the Omnibus package. I just created a template for this. It's pretty easy to get up and running, as this docker contains all necessary dependencies already (Redis, PostgreSQL, Nginx etc.). Application Name: GitLab-CE Application Site: https://gitlab.com/ Docker Hub: https://hub.docker.com/r/gitlab/gitlab-ce/ Github: https://github.com/gitlabhq/gitlabhq unRAID Template: https://github.com/tynor88/docker-templates Setup/Configuration: http://docs.gitlab.com/omnibus/docker/ Feel free to post any questions/issues/requests relating to this docker in this thread.

Does my private domain have to be registered or transferred to them? Or can it update a godaddy or some other domain? You will need to move them to UnoEuro in order to use this docker (or find a docker which can update GoDaddy domains).

How are you removing the files? This is just for files you delete over the network using SMB. Doh! Mostly through SSH (rm command) and FTP. But thanks for the clarification. Is there any way you can have like a recycle bin for rm commands?

I cannot get this plugin to work. I've attached a screenshot of my configuration, but for some reason no files i remove are inside the .Recycle.Bin folder (it's not even created). The only thing i see is some shortcuts inside /mnt/RecycleBin (but the the shortcuts points to nothing as there are no .Recycle.Bin folders in any of my shares).

I am getting something similar on 6.2.0-beta21 Warning: file_get_contents(/boot/config/smb-extra.conf): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(300) : eval()'d code on line 16