Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • A arch-boxes
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • David Runge
  • arch-boxes
  • Repository
Switch branch/tag
  • arch-boxes
  • http
  • install-chroot.sh
Find file BlameHistoryPermalink
  • Christian Rebischke's avatar
    Fix #41: ensure pacman-init finishes before sshd · 28d9964d
    Christian Rebischke authored Sep 10, 2019
    
    
    This is supposed to fix #41.
    Vagrant is able to provision boxes, therefore we need to make sure
    that the box has finished all Pacman keyring initialization before
    Vagrant is able to login via SSH and provision the box.
    Signed-off-by: default avatarChristian Rebischke <chris@nullday.de>
    28d9964d