Skip to content
GitLab
Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Snippets
  • Sign up now
  • Login
  • Sign in / Register
  • gitlab-runner gitlab-runner
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 2,604
    • Issues 2,604
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 108
    • Merge requests 108
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • gitlab-runnergitlab-runner
  • Issues
  • #4845
Closed
Open
Issue created Nov 01, 2019 by Steve Azzopardi@steveazzMaintainer

Have GitLab Runner package installation ignore skel when creating user home directory

Overview

We allow users to install GitLab Runner using a package repository, which creates a home directory and has the defaults skeleton directory specified in the machine. Debian buster breaks this because of the .bash_logout (issue #4449 (closed)). In !1523 (closed) we added a flag GITLAB_RUNNER_DISABLE_SKEL which allows user to remove the skel and have the home directory empty for the gitlab-runner user.

This flag is turned off by default for now to prevent breaking change.

Proposal

  • Turn on GITLAB_RUNNER_DISABLE_SKEL by default in %14.0 to prevent issues like this ever happening, if the user wants to have the skel generate they have to pass the flag explicitly.
  • Update the package repository to stop mentioning the SKEL that it's on by default
Edited Jun 05, 2021 by Mike Lockhart
Assignee
Assign to
Time tracking