2
1

Config.in 2.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106
  1. config BR2_TARGET_ROOTFS_OCI
  2. bool "oci image"
  3. depends on BR2_PACKAGE_HOST_GO_TARGET_ARCH_SUPPORTS
  4. help
  5. Build an OCI (Open Container Initiative) image.
  6. By default, the image is generated in a directory called
  7. rootfs-oci:
  8. $ cd output/images
  9. $ ls rootfs-oci/
  10. blobs index.json oci-layout
  11. You can push the image to a registry. Example using skopeo:
  12. $ skopeo copy --dest-creds <user>:<pass> \
  13. oci:rootfs-oci:<tag> docker://<user>/<image>[:tag]
  14. And pull/run it with docker:
  15. $ docker run -it <user>/<image>[:tag]
  16. if BR2_TARGET_ROOTFS_OCI
  17. config BR2_TARGET_ROOTFS_OCI_AUTHOR
  18. string "author name and/or email address"
  19. default "Buildroot"
  20. help
  21. Name and/or email address of the person which created the
  22. image.
  23. config BR2_TARGET_ROOTFS_OCI_TAG
  24. string "image tag"
  25. default "latest"
  26. help
  27. Tag to be used in the container image. If empty, 'latest' will
  28. be used by default.
  29. config BR2_TARGET_ROOTFS_OCI_ENTRYPOINT
  30. string "entrypoint"
  31. default "sh"
  32. help
  33. Command to execute when the container starts.
  34. Spaces must be quoted or escaped, like for a shell string:
  35. /usr/bin/env sh -c
  36. /bin/my-init --some-option "1 2 3 4" some\ arg --
  37. See the Docker documentation on how entrypoint and command
  38. interact together:
  39. https://docs.docker.com/engine/reference/builder/#understand-how-cmd-and-entrypoint-interact
  40. config BR2_TARGET_ROOTFS_OCI_CMD
  41. string "command (or entrypoint arguments)"
  42. help
  43. Default command, or entrypoint arguments, of the container.
  44. Spaces must be quoted or escaped, like for a shell string:
  45. "your shell scriptlet"
  46. /usr/bin/env sh
  47. See the Docker documentation on how entrypoint and command
  48. interact together:
  49. https://docs.docker.com/engine/reference/builder/#understand-how-cmd-and-entrypoint-interact
  50. config BR2_TARGET_ROOTFS_OCI_WORKDIR
  51. string "working directory"
  52. help
  53. Working directory of the entrypoint process in the
  54. container.
  55. config BR2_TARGET_ROOTFS_OCI_UID
  56. string "username or UID"
  57. default "0"
  58. help
  59. The username or UID of user the process run as.
  60. config BR2_TARGET_ROOTFS_OCI_ENV_VARS
  61. string "environment variables"
  62. help
  63. Default environment variables for the container.
  64. Space-separated list of variable=value assignments.
  65. config BR2_TARGET_ROOTFS_OCI_PORTS
  66. string "ports"
  67. help
  68. Default set of ports to expose from a container running
  69. this image as a space-separted list of ports in the following
  70. format:
  71. <port>/tcp, <port>/udp, <port> (same as <port>/tcp).
  72. config BR2_TARGET_ROOTFS_OCI_LABELS
  73. string "labels"
  74. help
  75. Metadata in the format KEY=VALUE for the container compliant
  76. with OCI annotation rules. If KEY starts with a dot, it will
  77. be prefixed with "org.opencontainers.image"
  78. (e.g. .url -> org.opencontainers.image.url).
  79. config BR2_TARGET_ROOTFS_OCI_ARCHIVE
  80. bool "pack oci image into a tar archive"
  81. help
  82. Select whether the image should be packed into a TAR archive.
  83. endif