Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #2404

Closed
Open
Created Dec 27, 2012 by Administrator@rootOwner

"sudo chmod -R ug+rwXs,o-rwx /home/git/repositories/" doesn't work under Debian 6.0.6

Created by: ufukbay

When I installed GitLab 4.0 on a clean Debian 6.0.6 installation and run "sudo -u gitlab -H bundle exec rake gitlab:check RAILS_ENV=production", it didn't pass the "Repo base access is drwsrws---?" check. Afore-mentioned check checks if the "/home/git/repositories" is "6770" and its only possible to chmod to "2770", so the Set UID bit can't be set on the owner due to security reasons under most Unix systems (at least that is what I came up with after doing some google search).

GitLab is running without errors though. I could create a new admin user, new project and push to it. I didn't have this GitLab check error on GitLab Version 3.1 which was installed before on the same server. Maybe this is a very specific behaviour on Debian 6.0.6 but I would like to know if not beeing able to chmod to "6770" has any side effects for GitLab.

gitolite

Assignee
Assign to
Time tracking