Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • G gitlab-pages
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 167
    • Issues 167
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 25
    • Merge requests 25
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • gitlab-pages
  • Issues
  • #239
Closed
Open
Created Aug 07, 2019 by Caleb Maclennan@alerque

Default build not statically compiled

It seems the old #4 (closed) issue has surfaced again. When compiling 1.5.0 using the very basic method of getting the source and running make (which does still have the Makefile line about export CGO_ENABLED := 0), I am ending up with a binary that is dynamically linked:

$ ldd /usr/bin/gitlab-pages
        linux-vdso.so.1 (0x00007fffefa66000)
        libc.so.6 => /usr/lib/libc.so.6 (0x00007f4cc69e8000)
        /lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007f4cc7b94000)

This is (if issue #4 (closed) is to be believed) causing this (**** = redacted value):

 sudo /usr/bin/gitlab-pages -config /etc/gitlab-pages/config.cfg -log-verbose
INFO[0000] GitLab Pages Daemon                           revision=a4ca360 version="1.5.0~beta.0.ga4ca360"
INFO[0000] URL: https://gitlab.com/gitlab-org/gitlab-pages 
DEBU[0000] Start daemon with configuration               admin-https-cert= admin-https-key= admin-https-listener= admin-secret-path= admin-unix-listener= artifacts-server="****/api/v4" artifacts-server-timeout=10 auth-client-id=**** auth-client-secret=**** auth-redirect-uri="****/auth" auth-secret=**** auth-server="****" daemon-gid=996 daemon-inplace-chroot=false daemon-uid=996 default-config-filename=config disable-cross-origin-requests=false domain=**** listen-http= listen-https= listen-proxy="127.0.0.1:8282" log-format=text metrics-address= pages-domain=**** pages-root=/srv/pages pages-status= redirect-http=false root-cert= root-key= status_path= use-http-2=true
DEBU[0000] Set up proxy listener                         listener="127.0.0.1:8282"
INFO[0000] running the daemon as unprivileged user       gid=996 in-place=false uid=996
INFO[0000] Missing SSL_CERT_FILE environment variable. HTTPS requests will fail 
ERRO[0000] start failed                                  error="fork/exec /gitlab-pages: no such file or directory"
FATA[0000]                                               error="fork/exec /gitlab-pages: no such file or directory"

My /srv/pages directory does exist with normal permissions and owned my the user I'm trying to run as (996).

Assignee
Assign to
Time tracking