Difference between revisions of "Ansible APK Module"

From Alpine Linux
Jump to: navigation, search
m (Added See Also: Ansible)
m (Categorized: Package Manager)
Line 60: Line 60:
=See Also=
=See Also=
[[Category:Package Manager]]

Revision as of 22:06, 19 September 2017

Underconstruction clock icon gray.svg
This material is work-in-progress ...

Do not follow instructions here until this notice is removed.
(Last edited by John3-16 on 19 Sep 2017.)

Alpine Linux uses APK for all package management. As of Ansible 2.0, there is an apk.py module included in Ansible that provides support for package management on Alpine Linux hosts. This document provides some playbook samples and explanations for using this Ansible module.

Details on Module Options


The 'name' option can contain a single package or list of packages to install.


The 'state' option specifies what you want to do with the listed package(s) - present (installed but not upgraded), latest (installed or upgraded), absent (removed). The option defaults to 'present', so this command will not upgrade a package that is already installed if 'state' is not specified as 'latest'.


It is always a good idea to include the 'update_cache' option, because the command might fail otherwise if the repository contains a newer version of the package than listed in the local package index. The name 'update_cache' is slightly misleading, because it actually refers to the package index, not the local package cache. The system repositories are specified in the /etc/apk/repositories file. Is there a separate cached index for each repository? What happens to specified repository?


The 'upgrade' option is a system-wide upgrade of all packages. If you want to upgrade specific packages, use 'state' = 'latest'.

available (Ansible 2.4)

The 'available' option only applies to the 'upgrade' option. According to the documentation: "During upgrade, reset versioned world dependencies and change logic to prefer replacing or downgrading packages (instead of holding them) if the currently installed package is no longer available from any repository." In other words, using 'available' makes downgrades possible.

repository (Ansible 2.4)

If the 'repository' option is not specified, 'apk' will use the system repository specified in /etc/apk/repositories. More specifically, it will always use the local package index, and that package index will be updated from the system repository specified in /etc/apk/repositories if 'update_cache' is set. If you specify a 'repository', 'apk' will use both the system repository and those specified in the command??? NEED TO VERIFY ??? Note that 'apk' will install the newest package if multiple versions of the same package are available in the package index(es). There are some quirks to the 'repository' option: - There is a bug for state='latest' when the 'repository' option is supplied. In this case, the 'repository' option appears to be ignored. - The 'upgrade' option appears to use both the system and and specified repositories, regardless of whether or not the 'update-cache' option is set.

Basic Package Installation

Package Present

# Update repositories and install "foo" package
- apk:
    name: foo
    update_cache: yes

Advanced Features

tagged repos

check doesn't do actual update

system upgrade / downgrade - Upgrades to newer repository will work (with or without update). Attempting to downgrade with the newer repository still in /etc/apk/repositories will not downgrade.

trigger service restart based upon package upgrade

      - name: upgrade available
          available: yes
          upgrade: yes
          update_cache: yes
          repository: '{{ REPO }}'
        register: result

      - debug:
          msg: "The openssh package was updated so we should restart the sshd service"
        notify: restart sshd
        changed_when: "'openssh' in result.packages"
        when: "'openssh' in result.packages"

      - name: restart sshd
        service: name=sshd state=restarted

See Also