File: mappings.md

package info (click to toggle)
distrobuilder 3.2-4
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 1,468 kB
  • sloc: sh: 204; makefile: 75
file content (40 lines) | stat: -rw-r--r-- 1,020 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
# Mappings

`mappings` describes an architecture mapping between the architectures from those used in Incus and those used by the distribution.
These mappings are useful if you for example want to build a `x86_64` image but the source tarball contains `amd64` as its architecture.

```yaml
mappings:
    architectures: <map>
    architecture_map: <string>
```

It's possible to specify a custom map using the `architectures` field.
Here's an example of a custom mapping:

```yaml
mappings:
    architectures:
        i686: i386
        x86_64: amd64
        armv7l: armhf
        aarch64: arm64
        ppc: powerpc
        ppc64: powerpc64
        ppc64le: ppc64el
```

The mapped architecture can be accessed via `Image.ArchitectureMapped` in the code or `image.architecture_mapped` in the definition file.

There are some preset mappings which can be used in the `architecture_map` field.
Those are:

* `alpinelinux`
* `altlinux`
* `archlinux`
* `centos`
* `debian`
* `funtoo`
* `gentoo`
* `plamolinux`
* `voidlinux`