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 6
    • Issues 6
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Arch Linux
  • arch-boxes
  • Issues
  • #88
Closed
Open
Created Feb 24, 2020 by Sven-Hendrik Haase@svenstaroContributor

[RFE] We might can drop all `systemctl enable cloud-init` lines

Created by: shibumi

Is your feature request related to a problem? Please describe. Right now we enable four cloud-init services manually. Cloud-init comes with a default cloud-init-generator placed in usr/lib/systemd/system-generators/cloud-init-generator. Therefore systemd will make sure to trigger cloud-init when we have a datasource.

Describe the solution you'd like Just remove all systemctl enable cloud-init* lines in our cloud-init.sh file.

This needs proper testing!

Edited Sep 29, 2020 by Kristian Klausen
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking