Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • stork stork
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 199
    • Issues 199
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 15
    • Merge requests 15
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • storkstork
  • Issues
  • #602

Closed
Open
Created Nov 01, 2021 by Andrei Pavel@andrei🐧Maintainer

update docs on how to set up rootless docker access

* [ ] Prefix every docker and docker-compose command in Rakefile with sudo to allow running rake commands as a normal user.

* Makes the entire rake command not enforce root on other subcommands which might not need it. * Makes leftover files to not be root-owned. Easier to cleanup. * Prevents the command to fail mid-way if you forgot to sudo it. Which then leaves the user wondering if they can continue with sudo or if they should clean up the artifacts created so far and start over.

UPDATE: will update the docs how to set up docker, so it doesn't require root access.

Edited Nov 08, 2021 by Andrei Pavel
Assignee
Assign to
Time tracking