kmachine | Docker machine variant to create a single node Kubernetes

by skippbox Go Version: v1.2.1 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | kmachine Summary

kmachine is a Go library typically used in Big Data, Docker, Spark, Hadoop applications. kmachine has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

kmachine lets you create Docker hosts on your computer, on cloud providers, and inside your own data center. It creates servers, installs Docker on them, then configures the Docker client to talk to them just like docker-machine. kmachine differs from Docker machine by also setting up a Kubernetes standalone system. Each component of Kubernetes are started as Docker containers. kmachine returns the configuration information necessary for kubectl to communicate to this remote k8s endpoint. The functionalities of docker-machine are preserved.

Support

Quality

Security

License

Reuse

Support

kmachine has a low active ecosystem.

It has 178 star(s) with 31 fork(s). There are 11 watchers for this library.

It had no major release in the last 12 months.

There are 10 open issues and 26 have been closed. On average issues are closed in 42 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of kmachine is v1.2.1

Quality

kmachine has 0 bugs and 0 code smells.

Security

kmachine has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

kmachine code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

kmachine is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

kmachine releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

It has 172296 lines of code, 9347 functions and 1447 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of kmachine

Get all kandi verified functions for this library.

kmachine Key Features

No Key Features are available at this moment for kmachine.

kmachine Examples and Code Snippets

No Code Snippets are available at this moment for kmachine.

Community Discussions

Trending Discussions on kmachine

Correct value for Yocto KMACHINE setting

QUESTION

Correct value for Yocto KMACHINE setting

Asked 2022-Jan-18 at 07:53

I'm trying to find the correct value for the KMACHINE setting, defined as "The machine as known by the kernel."

When I manually configure the kernel (outside of Yocto) I do not enter a machine type. I do set ARCH=arm, choose a "system type" config option like CONFIG_ARCH_LPC32XX=y, or load a defconfig like lpc32xx_defconfig but I don't know if any of those is what KMACHINE is supposed to be.

As an example, the Yocto documentation gives intel-core2-32 which does not appear anywhere the Linux 5.15 sources.

...

ANSWER

Answered 2022-Jan-18 at 07:53

KMACHINE is used to select Yocto-specific metadata for building the kernel, and is not passed to the kernel build system. By default, it is set to ${MACHINE} in kernel-yocto.bbclass, and can be overridden if a machine does not need its own metadata selection, and can instead use an existing metadata.

There's a better description under LINUX_KERNEL_TYPE in the manual (paraphrased):

The KMACHINE and LINUX_KERNEL_TYPE variables define the search arguments used by Yocto's kernel tools to find the appropriate description within Yocto's kernel metadata with which to build out the kernel sources and configuration.

This kernel metadata is maintained by the Yocto Project, in the yocto-kernel-cache repository. It is optional, and is only used if the selected kernel recipe is a "linux-yocto" style recipe (i.e. it inherits linux-yocto.inc).

If you're using an out-of-kernel-tree defconfig to configure your kernel, it's unlikely you'll need Yocto's kernel metadata, and therefore don't need to override KMACHINE.

Source https://stackoverflow.com/questions/70725893

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install kmachine

Get it from the [release page](https://github.com/skippbox/kmachine/releases). For windows users, you need just an other step. Look at [this doc](docs/kmachine-for-windows-users.md) please.
The build mechanism is identical to docker-machine, you need a Docker host and then:. or specify your OS and ARCH.

Support

kmachine is currently rebased on docker-machine 0.5.0 (latest) and all drivers are used the same way. The binaries are called kmachine. The configuration files are kept in ~/.kube/machine so that it does not interfere with an existing installation of docker-machine.

Find more information at: