TurnKey GitLab with Proxmox VE 7.3

R

RodMor

Member
Oct 11, 2022
10
0
6
Hello,

I'm trying to install the latest version of GitLab on Proxmox VE 7.3, in an LXC container.

For that, I came to the link:
https://www.turnkeylinux.org/gitlab

Which files should I download to send to Container templates in Proxmox and deploy the App?

Any thoughts will be welcome.

Thank you!
 
It is integratede into Proxmox: Use the GUI to go to a Storage that can contain CT Templates and press the Templates button. Select turnkey-gitlab and press download.
 
Hello,

Thanks for the feedback.
I experimented with this option and followed the installation instructions.
I entered my GitLab IP, entered the access credentials and the first message I see is:
500 - Whoops, something went wrong on our end.
Try refreshing the page, or going back and trying the action again.

I have already repeated this process 2 times without success, after having tried some commands that I saw in forums, but I did not get a good result.
I reinstalled everything a 3rd time and got the same result on this fresh installation.

Can you please tell me what I should do from here?
Any thoughts are welcome.
 
Sorry but I have no experience with TurnKey containers. I assume you did follow the set-up steps on their webpage. I have no idea what could be causing the very generic error 500.
 
Code: 
root@svr-lab:~# pct config 299
arch: amd64
cores: 4
features: nesting=1
hostname: GitLab
memory: 4096
net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=<MAC ADDRESS>,ip=dhcp,type=veth
ostype: debian
rootfs: HVDisk-Lab:299/vm-299-disk-0.raw,size=16G
swap: 2048
unprivileged: 1
root@svr-lab:~#
 
I had the same issue and it was fixed by not logging in as root but creating a new user then log in, then log out and re log in as root
 
  • Like
Reactions: Ptx
RodMor said:
I entered my GitLab IP, entered the access credentials and the first message I see is:
500 - Whoops, something went wrong on our end.
Try refreshing the page, or going back and trying the action again.
Click to expand...

I just got one running last night, and this is still an issue.


See here -> https://github.com/turnkeylinux/tracker/issues/1823

TL;DR:

Run this in container console
Bash: 
gitlab-rails runner -e production "ApplicationSetting.current.reset_runners_registration_token!"

And then this
Bash: 
/usr/lib/inithooks/bin/gitlab.py --email="your@mail.com" --domain="your.externail-domain.com"
 
You must log in or register to reply here.
Top Bottom