You are my saviour! I was fighting with QNAP's GitLab (with obsolete images) and then I found this video which made everything easy and fast! You forgot to mention that initial root password can be found inside "initial_root_password". Also I don't have nano installed on my machine so I used "vi".
sadly i do not meet the RAM requirements for setting up a Gitlab server on my NAS, however i did really like this video. Very clear and clean. You should have more views
Great tutorial - How would I get port 80 to forward to the container so I can get a LetsEncrypt certificate? When I add 80 to the host box in the container settings dialog it has a red border and it is removed when the container restarts.
I can install the gitlab server as you describe, but every time I stop and re-start the docker container, all my settling (user login etc) are lost. So I don't even have to commit anything, since I expect the same will happen. I'll assume this is due to the way how these docker containers work (keeping things in a virtual environment till you stop the container), so there is a huge gap in this video: how to avoid settling and folders get lost when the container is stopped. I would even like to have all the data outside of the container, in a share I can access as administrator.
The video is now 2 years old. I’ll try to make a new one soon that addresses these comments and concerns. I remember that happening to mine as well, but I don’t recall right now exactly what was the issue. The settings themselves are saved on those three folders: /var/log/gitlab; /var/opt/gitlab; /etc/gitlab Restarting should flush those settings.
@@FelipeBaezFilms I have the same problem. After restarting the device, new volumes were created and all configuration and data were overwritten. I have a backup of folders from "/ Container / container-station-data / lib / docker / volumes". I copied them to "share / gitlab" and provided the links during installation in the "Volume from host" section, but unfortunately the application does not start.
Hello, in my case, there is no link appearing in the Container Station. And also even when I’m going to add a domain in the gitlab.rb-Script and reboot the container, I run into an error. It would be great if you could give me information about how you managed this. Thank you. The Video is really good. Best Regards.
i found the other comment and reply, seems they are created when its the initial install. Another problem im having is it seems the container runs and gitlab installs, but the URL field never populates. the log is just showing a status 200 over and over again from a cron job. Do you have any videos on setting up the network settings for the container?
Hello I did see you tutorial I was looking for the way to edit the gitlab config, your video did show it.Thanx it did save me lots of time. Its the first container I run on my Qnap. I do see after the container runs, the 3 file paths are created on the NAS. Can you tell me whats the best way to backup the container or container config ? I run backup software on my qnap that already backups data to my cloudspace. Would like to backup gitlab aswell. If you know how let me know or make another great video :-)
Worked fine until container throw an error during reconfigure - has anyone solved that? There was an error running gitlab-ctl reconfigure: storage_directory[/var/opt/gitlab/.ssh] (gitlab::gitlab-shell line 34) had an error: Errno::EACCES: ruby_block[directory resource: / var/opt/gitlab/.ssh] (/opt/gitlab/embedded/cookbooks/cache/cookbooks/package/resources/storage_directory.rb line 34) had an error: E rrno::EACCES: Permission denied - set -x && [ -d "/var/opt/gitlab/.ssh" ]
It’s possible but I didn’t have any luck with it as the configuration file is not the same as the one from the gitlab documentations. Actually, quite a lot harder to get it configured properly. The container station/docker is by far the easiest, plus it’s nice it’s separate from the rest of the system.
AND, having that line wrong, like I had, in a recent update I wasn’t able to start the container anymore. Had to go find the gitlab.rb file to edit and then it came back.
