Permalink
Browse files

*: coreos/rkt -> rkt/rkt

  • Loading branch information...
jonboulle committed Apr 6, 2017
1 parent 03ed29d commit 5e6abc98db8a8f7e98315ad4312f2fab2decb335
Showing with 1,216 additions and 1,215 deletions.
  1. +569 −569 CHANGELOG.md
  2. +3 −3 Documentation/devel/cgroups.md
  3. +1 −1 Documentation/devel/distribution-point.md
  4. +1 −1 Documentation/devel/on-disk-format.md
  5. +3 −3 Documentation/devel/quickstart-dev.md
  6. +7 −7 Documentation/devel/release.md
  7. +1 −1 Documentation/devel/user-namespaces.md
  8. +10 −10 Documentation/distributions.md
  9. +1 −1 Documentation/getting-started-guide.md
  10. +3 −3 Documentation/hacking.md
  11. +1 −1 Documentation/install-rkt-in-coreos.md
  12. +1 −1 Documentation/integrations.md
  13. +1 −1 Documentation/networking/dns.md
  14. +3 −3 Documentation/packaging.md
  15. +4 −4 Documentation/performance/rkt-1-4-0-benchmarks.md
  16. +1 −1 Documentation/production-users.md
  17. +14 −14 Documentation/proposals/oci.md
  18. +1 −1 Documentation/rkt-build-rkt.md
  19. +3 −3 Documentation/subcommands/api-service.md
  20. +1 −1 Documentation/subcommands/metadata-service.md
  21. +4 −4 Documentation/trying-out-rkt.md
  22. +11 −11 README.md
  23. +5 −5 ROADMAP.md
  24. +1 −1 api/v1alpha/README.md
  25. +1 −1 api/v1alpha/api.pb.go
  26. +2 −2 api/v1alpha/api.proto
  27. +1 −1 api/v1alpha/client_example.go
  28. +2 −2 common/cgroup/cgroup.go
  29. +3 −3 common/cgroup/v1/cgroup.go
  30. +1 −1 common/common.go
  31. +1 −1 common/environment.go
  32. +1 −1 common/group.go
  33. +3 −3 common/mount.go
  34. +1 −1 common/overlay/overlay.go
  35. +2 −2 configure.ac
  36. +1 −1 dist/init/systemd/rkt-api.service
  37. +1 −1 dist/init/systemd/rkt-metadata.service
  38. +1 −1 glide.yaml
  39. +2 −2 lib/app.go
  40. +1 −1 lib/pod.go
  41. +1 −1 lib/types.go
  42. +1 −1 makelib/variables.mk
  43. +1 −1 makelib/verbosity.mk
  44. +4 −4 networking/kvm.go
  45. +1 −1 networking/net_plugin.go
  46. +4 −4 networking/networking.go
  47. +2 −2 networking/podenv.go
  48. +1 −1 networking/portfwd.go
  49. +2 −2 pkg/aci/render.go
  50. +2 −2 pkg/backup/backup.go
  51. +1 −1 pkg/distribution/appc.go
  52. +1 −1 pkg/fileutil/fileutil.go
  53. +1 −1 pkg/fileutil/fileutil_test.go
  54. +1 −1 pkg/keystore/keystore.go
  55. +1 −1 pkg/keystore/keystore_test.go
  56. +1 −1 pkg/label/label_selinux.go
  57. +1 −1 pkg/label/label_selinux_test.go
  58. +6 −6 pkg/pod/pods.go
  59. +1 −1 pkg/pod/pods_test.go
  60. +2 −2 pkg/pod/sandbox.go
  61. +1 −1 pkg/pod/wait.go
  62. +1 −1 pkg/selinux/selinux.go
  63. +1 −1 pkg/selinux/selinux_test.go
  64. +3 −3 pkg/tar/chroot.go
  65. +2 −2 pkg/tar/tar.go
  66. +3 −3 pkg/tar/tar_test.go
  67. +2 −2 pkg/user/resolver.go
  68. +1 −1 pkg/user/resolver_test.go
  69. +8 −8 rkt/api_service.go
  70. +3 −3 rkt/api_service_sdjournal.go
  71. +1 −1 rkt/api_service_stub.go
  72. +2 −2 rkt/api_service_test.go
  73. +1 −1 rkt/app.go
  74. +6 −6 rkt/app_add.go
  75. +1 −1 rkt/app_list.go
  76. +2 −2 rkt/app_rm.go
  77. +8 −8 rkt/app_sandbox.go
  78. +2 −2 rkt/app_start.go
  79. +1 −1 rkt/app_status.go
  80. +2 −2 rkt/app_stop.go
  81. +5 −5 rkt/attach.go
  82. +1 −1 rkt/cat_manifest.go
  83. +1 −1 rkt/cli_apps.go
  84. +1 −1 rkt/config/config.go
  85. +4 −4 rkt/enter.go
  86. +7 −7 rkt/export.go
  87. +5 −5 rkt/fetch.go
  88. +9 −9 rkt/fetch_test.go
  89. +1 −1 rkt/flag/secflags.go
  90. +5 −5 rkt/gc.go
  91. +1 −1 rkt/help.go
  92. +1 −1 rkt/image/asc.go
  93. +7 −7 rkt/image/common.go
  94. +1 −1 rkt/image/common_test.go
  95. +3 −3 rkt/image/dockerfetcher.go
  96. +6 −6 rkt/image/fetcher.go
  97. +3 −3 rkt/image/filefetcher.go
  98. +1 −1 rkt/image/finder.go
  99. +4 −4 rkt/image/httpfetcher.go
  100. +2 −2 rkt/image/httpops.go
  101. +2 −2 rkt/image/io.go
  102. +5 −5 rkt/image/namefetcher.go
  103. +2 −2 rkt/image/resumablesession.go
  104. +1 −1 rkt/image/validator.go
  105. +1 −1 rkt/image_cat_manifest.go
  106. +1 −1 rkt/image_cmd_common.go
  107. +1 −1 rkt/image_export.go
  108. +4 −4 rkt/image_extract.go
  109. +5 −5 rkt/image_gc.go
  110. +4 −4 rkt/image_list.go
  111. +4 −4 rkt/image_render.go
  112. +1 −1 rkt/image_rm.go
  113. +3 −3 rkt/list.go
  114. +1 −1 rkt/main.go
  115. +1 −1 rkt/metadata_service.go
  116. +8 −8 rkt/prepare.go
  117. +3 −3 rkt/pubkey/pubkey.go
  118. +5 −5 rkt/rkt.go
  119. +1 −1 rkt/rkt_test.go
  120. +1 −1 rkt/rm.go
  121. +9 −9 rkt/run.go
  122. +5 −5 rkt/run_prepared.go
  123. +4 −4 rkt/stage1hash.go
  124. +2 −2 rkt/status.go
  125. +2 −2 rkt/stop.go
  126. +2 −2 rkt/trust.go
  127. +1 −1 rkt/version.go
  128. +2 −2 scripts/changelog.sh
  129. +1 −1 scripts/genproto.sh
  130. +2 −2 scripts/glide-update.sh
  131. +2 −2 scripts/install-rkt.sh
  132. +1 −1 scripts/pkg/build-pkgs.sh
  133. +4 −4 stage0/app_add.go
  134. +2 −2 stage0/app_rm.go
  135. +2 −2 stage0/app_start.go
  136. +2 −2 stage0/app_stop.go
  137. +5 −4 stage0/common.go
  138. +1 −1 stage0/gc.go
  139. +1 −1 stage0/log.go
  140. +1 −1 stage0/manifest.go
  141. +2 −2 stage0/registration.go
  142. +13 −13 stage0/run.go
  143. +1 −1 stage0/stop.go
  144. +6 −6 stage1/app_add/app_add.go
  145. +5 −5 stage1/app_rm/app_rm.go
  146. +3 −3 stage1/app_start/app_start.go
  147. +4 −4 stage1/app_stop/app_stop.go
  148. +3 −3 stage1/attach/attach.go
  149. +2 −2 stage1/common/run.go
  150. +3 −3 stage1/common/ssh/ssh.go
  151. +2 −2 stage1/common/types/pod.go
  152. +2 −2 stage1/enter_kvm/enter_kvm.go
  153. +6 −6 stage1/gc/gc.go
  154. +3 −3 stage1/init/common/app.go
  155. +2 −2 stage1/init/common/dns_config.go
  156. +1 −1 stage1/init/common/log.go
  157. +4 −4 stage1/init/common/mount.go
  158. +1 −1 stage1/init/common/path.go
  159. +5 −5 stage1/init/common/pod.go
  160. +1 −1 stage1/init/common/pod_test.go
  161. +1 −1 stage1/init/common/seccomp.go
  162. +3 −3 stage1/init/common/units.go
  163. +19 −19 stage1/init/init.go
  164. +6 −6 stage1/init/kvm.go
  165. +2 −2 stage1/init/kvm/hypervisor/hvlkvm/lkvm_driver.go
  166. +2 −2 stage1/init/kvm/hypervisor/hvqemu/qemu_driver.go
  167. +1 −1 stage1/init/kvm/log.go
  168. +1 −1 stage1/init/kvm/network.go
  169. +2 −2 stage1/iottymux/iottymux.go
  170. +1 −1 stage1/prepare-app/prepare-app.c
  171. +2 −2 stage1/stop_kvm/stop_kvm.go
  172. +1 −1 stage1/usr_from_coreos/cache.sh
  173. +1 −1 stage1_fly/enter/main.go
  174. +2 −2 stage1_fly/gc/main.go
  175. +12 −12 stage1_fly/run/main.go
  176. +1 −1 store/db/db.go
  177. +1 −1 store/db/db_test.go
  178. +1 −1 store/imagestore/main_test.go
  179. +1 −1 store/imagestore/migrate_test.go
  180. +3 −3 store/imagestore/store.go
  181. +3 −3 store/imagestore/store_test.go
  182. +6 −6 store/treestore/tree.go
  183. +4 −4 store/treestore/tree_test.go
  184. +1 −1 tests/echo-socket-activated/echo-socket-activated.go
  185. +4 −4 tests/inspect/inspect.go
  186. +1 −1 tests/rkt_ace_validator_test.go
  187. +2 −2 tests/rkt_api_service_bench_test.go
  188. +3 −3 tests/rkt_api_service_test.go
  189. +1 −1 tests/rkt_app_isolator_nspawn_test.go
  190. +2 −2 tests/rkt_app_isolator_test.go
  191. +2 −2 tests/rkt_app_sandbox_test.go
  192. +1 −1 tests/rkt_attach_test.go
  193. +2 −2 tests/rkt_auth_test.go
  194. +1 −1 tests/rkt_caps_test.go
  195. +1 −1 tests/rkt_cat_manifest_test.go
  196. +1 −1 tests/rkt_config_test.go
  197. +1 −1 tests/rkt_devices_test.go
  198. +1 −1 tests/rkt_diagnostic_test.go
  199. +1 −1 tests/rkt_dns_test.go
  200. +1 −1 tests/rkt_env_test.go
  201. +1 −1 tests/rkt_error_output_test.go
  202. +2 −2 tests/rkt_etc_hosts_test.go
  203. +2 −2 tests/rkt_exec_test.go
  204. +2 −2 tests/rkt_exit_test.go
  205. +2 −2 tests/rkt_export_container_test.go
  206. +2 −2 tests/rkt_export_fly_test.go
  207. +1 −1 tests/rkt_export_test.go
  208. +5 −5 tests/rkt_fetch_test.go
  209. +1 −1 tests/rkt_fly_test.go
  210. +1 −1 tests/rkt_gc_nspawn_test.go
  211. +2 −2 tests/rkt_gc_test.go
  212. +1 −1 tests/rkt_hostname_test.go
  213. +2 −2 tests/rkt_image_cat_manifest_test.go
  214. +6 −6 tests/rkt_image_dependencies_test.go
  215. +2 −2 tests/rkt_image_export_test.go
  216. +1 −1 tests/rkt_image_extract_test.go
  217. +2 −2 tests/rkt_image_gc_test.go
  218. +3 −3 tests/rkt_image_list_test.go
  219. +2 −2 tests/rkt_image_render_test.go
  220. +1 −1 tests/rkt_image_rm_test.go
  221. +1 −1 tests/rkt_interactive_test.go
  222. +1 −1 tests/rkt_journal_test.go
  223. +1 −1 tests/rkt_list_test.go
  224. +1 −1 tests/rkt_metadata_service_test.go
  225. +2 −2 tests/rkt_mount_overlay_test.go
  226. +1 −1 tests/rkt_mount_test.go
  227. +1 −1 tests/rkt_mountns_test.go
  228. +1 −1 tests/rkt_mtab_test.go
  229. +4 −4 tests/rkt_net_test.go
  230. +1 −1 tests/rkt_no_new_privs_test.go
  231. +2 −2 tests/rkt_non_root_test.go
  232. +1 −1 tests/rkt_oom_score_adj_test.go
  233. +2 −2 tests/rkt_os_arch_test.go
  234. +2 −2 tests/rkt_paths_test.go
  235. +1 −1 tests/rkt_pid_file_test.go
  236. +1 −1 tests/rkt_prepare_test.go
  237. +1 −1 tests/rkt_rm_nspawn_test.go
  238. +1 −1 tests/rkt_rm_test.go
  239. +1 −1 tests/rkt_root_commands_test.go
  240. +2 −2 tests/rkt_run_pod_manifest_test.go
  241. +1 −1 tests/rkt_run_test.go
  242. +2 −2 tests/rkt_run_user_group_test.go
  243. +1 −1 tests/rkt_seccomp_test.go
  244. +1 −1 tests/rkt_service_file_test.go
  245. +1 −1 tests/rkt_socket_activation_test.go
  246. +2 −2 tests/rkt_socket_proxyd_test.go
  247. +3 −3 tests/rkt_stage1_loading_test.go
  248. +1 −1 tests/rkt_stop_test.go
  249. +1 −1 tests/rkt_supplementary_gids_test.go
  250. +4 −4 tests/rkt_tests.go
  251. +1 −1 tests/rkt_trust_test.go
  252. +3 −3 tests/rkt_userns_test.go
  253. +1 −1 tests/rkt_volume_mount_test.go
  254. +2 −2 tests/rkt_volume_nspawn_test.go
  255. +1 −1 tests/rkt_volume_test.go
  256. +3 −3 tests/stub-stage1/run/main.go
  257. +1 −1 tests/testutils/ctx.go
  258. +1 −1 tests/testutils/datadirsetup.go
  259. +1 −1 tests/testutils/httputils.go
  260. +2 −2 tools/cleangen/main.go
  261. +2 −2 tools/depsgen/globcmd.go
  262. +2 −2 tools/depsgen/gocmd.go
  263. +1 −1 tools/depsgen/kvcmd.go
  264. +1 −1 tools/depsgen/main.go
  265. +1 −1 tools/depsgen/util.go
  266. +2 −2 tools/filelistgen/main.go
  267. +1 −1 tools/quickrm/main.go
View
1,138 CHANGELOG.md

Large diffs are not rendered by default.

Oops, something went wrong.
@@ -80,8 +80,8 @@ This is not implemented yet.
This could be implemented with cgroups.
[cgroups]: https://www.kernel.org/doc/Documentation/cgroup-v1/cgroups.txt
[machinedRegister]: https://github.com/coreos/rkt/blob/master/stage1/init/init.go#L153
[machinedRegister]: https://github.com/rkt/rkt/blob/master/stage1/init/init.go#L153
[network-isolator]: https://github.com/appc/spec/blob/master/spec/ace.md#resourcenetwork-bandwidth
[rkt-1757]: https://github.com/coreos/rkt/issues/1757
[rkt-1844]: https://github.com/coreos/rkt/pull/1844
[rkt-1757]: https://github.com/rkt/rkt/issues/1757
[rkt-1844]: https://github.com/rkt/rkt/pull/1844
[rkt-systemd]: ../using-rkt-with-systemd.md
@@ -165,4 +165,4 @@ For example there may exist multiple transport plugins (file, http, s3, bittorre
[docker2aci_GH]: https://github.com/appc/docker2aci
[oci_image_spec_readme]: https://github.com/opencontainers/image-spec#running-an-oci-imag://github.com/appc/docker2aci
[oci_layout]: https://github.com/opencontainers/image-spec/blob/master/image-layout.md
[rkt-2964]: https://github.com/coreos/rkt/pull/2964
[rkt-2964]: https://github.com/rkt/rkt/pull/2964
@@ -29,5 +29,5 @@ The [configuration][configuration] on-disk format is documented separately.
[configuration]: ../configuration.md
[pod-lifecycle]: pod-lifecycle.md
[rkt-706]: https://github.com/coreos/rkt/issues/706
[rkt-706]: https://github.com/rkt/rkt/issues/706
[rktkind-paths]: ../configuration.md#rktkind-paths
@@ -8,10 +8,10 @@ In this example ~/Repos is a personal workspace where all repos are stored
```sh
$ mkdir ~/Repos && cd ~/Repos
$ mkdir -p ~/.local/gopath/src/github.com/coreos
$ mkdir -p ~/.local/gopath/src/github.com/rkt
$ sudo apt-get install git
$ git -C ~/.local/gopath/src/github.com/coreos clone https://github.com/coreos/rkt.git
$ ln -s ~/.local/gopath/src/github.com/coreos/rkt rkt
$ git -C ~/.local/gopath/src/github.com/rkt clone https://github.com/rkt/rkt.git
$ ln -s ~/.local/gopath/src/github.com/rkt/rkt rkt
```
On a fresh system installation, few additional software packages are needed to correctly build rkt:
@@ -23,7 +23,7 @@ The following example assumes we're going from version 1.1.0 (`v1.1.0`) to 1.2.0
Let's get started:
- Start at the relevant milestone on GitHub (e.g. https://github.com/coreos/rkt/milestones/v1.2.0): ensure all referenced issues are closed (or moved elsewhere, if they're not done). Close the milestone.
- Start at the relevant milestone on GitHub (e.g. https://github.com/rkt/rkt/milestones/v1.2.0): ensure all referenced issues are closed (or moved elsewhere, if they're not done). Close the milestone.
- Update the [roadmap][roadmap] to remove the release you're performing, if necessary
- Ensure that `stage1/aci/aci-manifest.in` is the same version of appc/spec vendored with rkt. Otherwise, update it.
- Branch from the latest master, make sure your git status is clean
@@ -122,11 +122,11 @@ git log v1.1.0..v1.2.0 --pretty=format:"%an" | sort | uniq | tr '\n' ',' | sed -
```
[changelog]: https://github.com/coreos/rkt/blob/master/CHANGELOG.md
[configure_ac]: https://github.com/coreos/rkt/blob/master/configure.ac#L2
[changelog]: https://github.com/rkt/rkt/blob/master/CHANGELOG.md
[configure_ac]: https://github.com/rkt/rkt/blob/master/configure.ac#L2
[coreos-key]: https://coreos.com/security/app-signing-key
[gh-new-release]: https://github.com/coreos/rkt/releases/new
[milestones]: https://github.com/coreos/rkt/milestones
[maintainers]: https://github.com/coreos/rkt/blob/master/MAINTAINERS
[gh-new-release]: https://github.com/rkt/rkt/releases/new
[milestones]: https://github.com/rkt/rkt/milestones
[maintainers]: https://github.com/rkt/rkt/blob/master/MAINTAINERS
[rkt-dev-list]: https://groups.google.com/forum/#!forum/rkt-dev
[roadmap]: https://github.com/coreos/rkt/blob/master/ROADMAP.md
[roadmap]: https://github.com/rkt/rkt/blob/master/ROADMAP.md
@@ -36,4 +36,4 @@ It would make it work with overlayfs.
When mounting a volume from the host into the pod, the ownership of the files is not shifted, so it makes volumes difficult if not impossible to use with user namespaces.
The same kernel support should help here too ([#1057][rkt-1057]).
[rkt-1057]: https://github.com/coreos/rkt/issues/1057
[rkt-1057]: https://github.com/rkt/rkt/issues/1057
@@ -141,17 +141,17 @@ upgrade manually.
### rpm-based
```
gpg --recv-key 18AD5014C99EF7E3BA5F6CE950BDD3E0FC8A365E
wget https://github.com/coreos/rkt/releases/download/v1.25.0/rkt-1.25.0-1.x86_64.rpm
wget https://github.com/coreos/rkt/releases/download/v1.25.0/rkt-1.25.0-1.x86_64.rpm.asc
wget https://github.com/rkt/rkt/releases/download/v1.25.0/rkt-1.25.0-1.x86_64.rpm
wget https://github.com/rkt/rkt/releases/download/v1.25.0/rkt-1.25.0-1.x86_64.rpm.asc
gpg --verify rkt-1.25.0-1.x86_64.rpm.asc
sudo rpm -Uvh rkt-1.25.0-1.x86_64.rpm
```
### deb-based
```
gpg --recv-key 18AD5014C99EF7E3BA5F6CE950BDD3E0FC8A365E
wget https://github.com/coreos/rkt/releases/download/v1.25.0/rkt_1.25.0-1_amd64.deb
wget https://github.com/coreos/rkt/releases/download/v1.25.0/rkt_1.25.0-1_amd64.deb.asc
wget https://github.com/rkt/rkt/releases/download/v1.25.0/rkt_1.25.0-1_amd64.deb
wget https://github.com/rkt/rkt/releases/download/v1.25.0/rkt_1.25.0-1_amd64.deb.asc
gpg --verify rkt_1.25.0-1_amd64.deb.asc
sudo dpkg -i rkt_1.25.0-1_amd64.deb
```
@@ -170,10 +170,10 @@ sudo dpkg -i rkt_1.25.0-1_amd64.deb
[rkt-nixos]: https://github.com/NixOS/nixpkgs/blob/master/pkgs/applications/virtualization/rkt/default.nix
[rkt-opensuse]: https://build.opensuse.org/package/show/Virtualization:containers/rkt
[rkt-void]: https://github.com/voidlinux/void-packages/tree/master/srcpkgs/rkt
[rkt-1305]: https://github.com/coreos/rkt/issues/1305
[rkt-1978]: https://github.com/coreos/rkt/issues/1978
[rkt-2206]: https://github.com/coreos/rkt/issues/2206
[rkt-2322]: https://github.com/coreos/rkt/issues/2322
[rkt-2325]: https://github.com/coreos/rkt/issues/2325
[rkt-2326]: https://github.com/coreos/rkt/issues/2326
[rkt-1305]: https://github.com/rkt/rkt/issues/1305
[rkt-1978]: https://github.com/rkt/rkt/issues/1978
[rkt-2206]: https://github.com/rkt/rkt/issues/2206
[rkt-2322]: https://github.com/rkt/rkt/issues/2322
[rkt-2325]: https://github.com/rkt/rkt/issues/2325
[rkt-2326]: https://github.com/rkt/rkt/issues/2326
[void-packages]: http://www.voidlinux.eu/packages/
@@ -96,5 +96,5 @@ hello
[appc-spec]: https://github.com/appc/spec
[rkt-daemon]: subcommands/run.md#run-rkt-as-a-daemon
[rkt-releases]: https://github.com/containers/build/releases
[rkt-vagrant]: https://github.com/coreos/rkt/blob/master/Documentation/trying-out-rkt.md#rkt-using-vagrant
[rkt-vagrant]: https://github.com/rkt/rkt/blob/master/Documentation/trying-out-rkt.md#rkt-using-vagrant
[signing-guide]: signing-and-verification-guide.md
View
@@ -7,15 +7,15 @@ For more information on the rkt internals, see the [`devel`](devel/) documentati
## Building rkt
The easiest way to build rkt is by using the coreos.com/rkt/builder ACI image. See instructions for how to use it in the README at [github.com/coreos/rkt-builder][rkt-builder].
The easiest way to build rkt is by using the coreos.com/rkt/builder ACI image. See instructions for how to use it in the README at [github.com/rkt/rkt-builder][rkt-builder].
Alternatively, you should be able build rkt on any modern Linux system with [Go](https://golang.org/) (1.5+) installed.
For the most part the codebase is self-contained (e.g. all dependencies are vendored), but assembly of the stage1 requires some other tools to be installed on the system.
Please see [the list of the build-time dependencies][build-time-dependencies].
Once the dependencies have been satisfied you can build rkt with a default configuration by running the following commands:
```
git clone https://github.com/coreos/rkt.git
git clone https://github.com/rkt/rkt.git
cd rkt
./autogen.sh && ./configure && make
```
@@ -210,6 +210,6 @@ If something looks awry, restart, pray to your preferred deity, and try again.
[glide-vc]: https://github.com/sgotti/glide-vc
[glide-versioning]: https://glide.readthedocs.io/en/latest/versions/
[go]: https://golang.org/
[rkt-builder]: https://github.com/coreos/rkt-builder
[rkt-builder]: https://github.com/rkt/rkt-builder
[run-time-dependencies]: dependencies.md#run-time-dependencies
[update-coreos-stage1]: devel/update-coreos-stage1.md
@@ -33,6 +33,6 @@ Other units being added can then contain a `After=rkt-install.service` (or
whatever the service was named) to delay their running until rkt has been
installed.
[rkt-releases]: https://github.com/coreos/rkt/releases
[rkt-releases]: https://github.com/rkt/rkt/releases
[ignition]: https://coreos.com/ignition/docs/latest/
[cloud-config]: https://coreos.com/os/docs/latest/cloud-config.html
@@ -1,5 +1,5 @@
# Integrations
This document tracks projects that integrate with rkt. [Join the community](https://github.com/coreos/rkt/), and help us keep the list up-to-date.
This document tracks projects that integrate with rkt. [Join the community](https://github.com/rkt/rkt/), and help us keep the list up-to-date.
## Projects
[Kubernetes](https://kubernetes.io/docs/getting-started-guides/rkt/): a enterprise grade container orchestration solution. Kubernetes offers rkt support as an alternative to the standard install.
@@ -113,4 +113,4 @@ round-trip min/avg/max = 5.421/5.421/5.421 ms
```
[standard-defaults]: https://github.com/coreos/rkt/blob/master/stage1/net/rootfs/etc/hosts-fallback
[standard-defaults]: https://github.com/rkt/rkt/blob/master/stage1/net/rootfs/etc/hosts-fallback
@@ -61,7 +61,7 @@ A few [example systemd unit files for rkt helper services][rkt-units] are includ
[rkt-gc]: subcommands/gc.md
[rkt-metadata-svc]: subcommands/metadata-service.md
[api-service]: subcommands/api-service.md
[rkt-units]: https://github.com/coreos/rkt/tree/master/dist/init/systemd
[rkt-vendor]: https://github.com/coreos/rkt/tree/master/vendor
[rkt-units]: https://github.com/rkt/rkt/tree/master/dist/init/systemd
[rkt-vendor]: https://github.com/rkt/rkt/tree/master/vendor
[run-deps]: dependencies.md#run-time-dependencies
[rkt-dirs]: https://github.com/coreos/rkt/blob/master/dist/init/systemd/tmpfiles.d/rkt.conf
[rkt-dirs]: https://github.com/rkt/rkt/blob/master/dist/init/systemd/tmpfiles.d/rkt.conf
@@ -12,7 +12,7 @@ Linux proton 4.4.6 #1-NixOS SMP Wed Mar 16 15:43:17 UTC 2016 x86_64 GNU/Linux
### log-stresser.aci
```
derek@proton ~/go/src/github.com/coreos/rkt/tests/rkt-monitor> sudo ./rkt-monitor log-stresser.aci
derek@proton ~/go/src/github.com/rkt/rkt/tests/rkt-monitor> sudo ./rkt-monitor log-stresser.aci
rkt(18493): seconds alive: 10 avg CPU: 28.314541% avg Mem: 2 mB peak Mem: 2 mB
systemd(18515): seconds alive: 9 avg CPU: 0.000000% avg Mem: 4 mB peak Mem: 4 mB
systemd-journal(18517): seconds alive: 9 avg CPU: 88.397098% avg Mem: 7 mB peak Mem: 7 mB
@@ -25,7 +25,7 @@ container stop time: 17332926ns
### mem-stresser.aci
```
derek@proton ~/go/src/github.com/coreos/rkt/tests/rkt-monitor> sudo ./rkt-monitor mem-stresser.aci
derek@proton ~/go/src/github.com/rkt/rkt/tests/rkt-monitor> sudo ./rkt-monitor mem-stresser.aci
worker(18634): seconds alive: 9 avg CPU: 98.550401% avg Mem: 318 mB peak Mem: 555 mB
rkt(18599): seconds alive: 10 avg CPU: 3.583814% avg Mem: 2 mB peak Mem: 2 mB
systemd(18628): seconds alive: 9 avg CPU: 0.000000% avg Mem: 4 mB peak Mem: 4 mB
@@ -37,7 +37,7 @@ container stop time: 17593446ns
### cpu-stresser.aci
```
derek@proton ~/go/src/github.com/coreos/rkt/tests/rkt-monitor> sudo ./rkt-monitor cpu-stresser.aci
derek@proton ~/go/src/github.com/rkt/rkt/tests/rkt-monitor> sudo ./rkt-monitor cpu-stresser.aci
rkt(18706): seconds alive: 10 avg CPU: 3.587050% avg Mem: 2 mB peak Mem: 2 mB
systemd(18736): seconds alive: 9 avg CPU: 0.000000% avg Mem: 4 mB peak Mem: 4 mB
systemd-journal(18740): seconds alive: 9 avg CPU: 0.000000% avg Mem: 6 mB peak Mem: 6 mB
@@ -49,7 +49,7 @@ container stop time: 16124700ns
### too-many-apps.podmanifest
```
derek@proton ~/go/src/github.com/coreos/rkt/tests/rkt-monitor> sudo ./rkt-monitor too-many-apps.podmanifest -d 30s
derek@proton ~/go/src/github.com/rkt/rkt/tests/rkt-monitor> sudo ./rkt-monitor too-many-apps.podmanifest -d 30s
# Identical (aside from PID) worker-binary lines removed
rkt(17227): seconds alive: 20 avg CPU: 9.595387% avg Mem: 3 mB peak Mem: 20 mB
systemd(17253): seconds alive: 17 avg CPU: 0.329028% avg Mem: 16 mB peak Mem: 16 mB
@@ -1,6 +1,6 @@
# Production users
This document tracks people and use cases for rkt in production. [Join the community](https://github.com/coreos/rkt/), and help us keep the list up-to-date.
This document tracks people and use cases for rkt in production. [Join the community](https://github.com/rkt/rkt/), and help us keep the list up-to-date.
## [BlaBlaCar](https://www.blablacar.com/)
@@ -9,13 +9,13 @@ This new specification differs considerably from rkt's internal ACI-based image
The internal rkt image handling is currently divided in three subsystems:
- **fetching**: This subsystem is responsible for downloading images of various types.
Non-ACI image types (Docker and OCI) are converted to ACI images by delegating to [docker2aci][docker2aci]. The logic resides in the `github.com/coreos/rkt/rkt/image` package.
Non-ACI image types (Docker and OCI) are converted to ACI images by delegating to [docker2aci][docker2aci]. The logic resides in the `github.com/rkt/rkt/rkt/image` package.
- **image store**: The image store is responsible for persisting and managing downloaded images.
It consists of two parts, a directory tree storing the actual image file blobs (usually residing under `/var/lib/rkt/cas/blob`) and a separate embedded SQL database storing image metadata usually residing in `/var/lib/rkt/cas/db/ql.db`. The implementation resides in the `github.com/coreos/rkt/store/imagestore` package.
It consists of two parts, a directory tree storing the actual image file blobs (usually residing under `/var/lib/rkt/cas/blob`) and a separate embedded SQL database storing image metadata usually residing in `/var/lib/rkt/cas/db/ql.db`. The implementation resides in the `github.com/rkt/rkt/store/imagestore` package.
- **tree store**: Since dependencies between ACI images form a directed acyclic graph according to the [appc spec][ace-fs] they are pre-rendered in a directory called the tree store cache.
If the [overlay filesystem](https://www.kernel.org/doc/Documentation/filesystems/overlayfs.txt) is enabled, the pre-rendered image is used as the `lowerdir` for the pod's rendered rootfs. The implementation resides in the `github.com/coreos/rkt/store/treestore` package.
If the [overlay filesystem](https://www.kernel.org/doc/Documentation/filesystems/overlayfs.txt) is enabled, the pre-rendered image is used as the `lowerdir` for the pod's rendered rootfs. The implementation resides in the `github.com/rkt/rkt/store/treestore` package.
The actual internal lifecycle of an image is documented in the [architecture documentation][image-lifecycle].
@@ -26,7 +26,7 @@ The following table gives an overview of the relevant differences between OCI an
Dependencies | Layers array in the [image manifest][oci-manifest] | [Dependency graph][ace-fs]
Hash algorithms | Potentially multiple [algorithms][oci-algorithms], but SHA-256 preferred | [SHA-512][appc-image-id-type]
Current ongoing work to support OCI in rkt is tracked in the following Github project: [https://github.com/coreos/rkt/projects/4](https://github.com/coreos/rkt/projects/4).
Current ongoing work to support OCI in rkt is tracked in the following Github project: [https://github.com/rkt/rkt/projects/4](https://github.com/rkt/rkt/projects/4).
### Goals, non-Goals
@@ -43,7 +43,7 @@ This document outlines the following necessary steps and references existing wor
3. Transport handlers
4. Tree store support for OCI
A non-goal is the implementation of the [OCI runtime specification][oci-runtime]. There is ongoing work in [https://github.com/coreos/rkt/issues/3408](https://github.com/coreos/rkt/issues/3408) covering this topic.
A non-goal is the implementation of the [OCI runtime specification][oci-runtime]. There is ongoing work in [https://github.com/rkt/rkt/issues/3408](https://github.com/rkt/rkt/issues/3408) covering this topic.
### Overview
@@ -64,8 +64,8 @@ The design document can be found in [Documentation/devel/distribution-point.md][
###### Status
- The design document (https://github.com/coreos/rkt/pull/2953) is merged.
- The implementation (https://github.com/coreos/rkt/pull/3369) is merged.
- The design document (https://github.com/rkt/rkt/pull/2953) is merged.
- The implementation (https://github.com/rkt/rkt/pull/3369) is merged.
###### TODOs
@@ -84,8 +84,8 @@ In order to prepare native support for OCI the following changes need to be impl
###### Status
- The design and initial implementation is proposed in https://github.com/coreos/rkt/pull/3071.
- The actual design document of the above PR can be found in [Documentation/proposals/reference_based_image_access_and_cas_store.md](https://github.com/coreos/rkt/blob/23313af1c3dac2fb24fe41f9a7c5eaca573e45dd/Documentation/proposals/reference_based_image_access_and_cas_store.md).
- The design and initial implementation is proposed in https://github.com/rkt/rkt/pull/3071.
- The actual design document of the above PR can be found in [Documentation/proposals/reference_based_image_access_and_cas_store.md](https://github.com/rkt/rkt/blob/23313af1c3dac2fb24fe41f9a7c5eaca573e45dd/Documentation/proposals/reference_based_image_access_and_cas_store.md).
Note that the above design document also suggests the introduction of a new key/value [Bolt](https://github.com/boltdb/bolt) based store. The current consensus is that the replacement of `ql` as the backing store can be done independently and therefore should be a non-goal for the OCI roadmap.
@@ -102,9 +102,9 @@ The current implementation makes it hard to integrate separate fetching subsyste
The current proposal is to abstract fetching logic behind "transport handlers" allowing for independent (potentially swappable) fetching implementations for the various image formats.
- A first initial design is proposed in https://github.com/coreos/rkt/pull/2964.
- A first initial design is proposed in https://github.com/rkt/rkt/pull/2964.
- The actual design document of the above PR can be found in [Documentation/proposal/fetchers_refactor.md](https://github.com/sgotti/rkt/blob/239fdff081f9fd47dd08834a5660a1375ea4771d/Documentation/proposal/fetchers_refactor.md).
- A first initial implementation is proposed in https://github.com/coreos/rkt/pull/3232.
- A first initial implementation is proposed in https://github.com/rkt/rkt/pull/3232.
Note that the initial design and implementation are in very early stage and should only be considered inspirational.
@@ -139,6 +139,6 @@ Backwards compatibility: Currently the biggest concern identified is backwards c
[oci-algorithms]: https://github.com/opencontainers/image-spec/blob/v1.0.0-rc2/descriptor.md#algorithms
[oci-image-layout]: https://github.com/opencontainers/image-spec/blob/v1.0.0-rc2/image-layout.md
[app-container]: https://github.com/coreos/rkt/blob/v1.25.0/Documentation/app-container.md
[image-lifecycle]: https://github.com/coreos/rkt/blob/v1.25.0/Documentation/devel/architecture.md#image-lifecycle
[distribution-point]: https://github.com/coreos/rkt/blob/v1.25.0/Documentation/devel/distribution-point.md
[app-container]: https://github.com/rkt/rkt/blob/v1.25.0/Documentation/app-container.md
[image-lifecycle]: https://github.com/rkt/rkt/blob/v1.25.0/Documentation/devel/architecture.md#image-lifecycle
[distribution-point]: https://github.com/rkt/rkt/blob/v1.25.0/Documentation/devel/distribution-point.md
@@ -15,7 +15,7 @@ export BUILDDIR=
mkdir -p $BUILDDIR
```
Start the container which will run the [rkt builder](https://github.com/coreos/rkt-builder), and compile rkt:
Start the container which will run the [rkt builder](https://github.com/rkt/rkt-builder), and compile rkt:
```
./scripts/build-rir.sh
```
Oops, something went wrong.

0 comments on commit 5e6abc9

Please sign in to comment.