- @onlyacello
- @aprakasa3
- @Fenita79269111
- @arezyadi
- @moechyarul
- @rio85851
- @bct215
- @NovarisAji
2024/07/17 15:22:51 Starting build run: vmware-vmx.box | |
2024/07/17 15:22:51 Running builder: vmware-vmx | |
2024/07/17 15:22:51 [INFO] (telemetry) Starting builder vmware-vmx.box | |
2024/07/17 15:22:51 packer-plugin-vmware_v1.0.11_x5.0_linux_amd64 plugin: 2024/07/17 15:22:51 VMware app path: /usr/bin/vmware | |
2024/07/17 15:22:51 packer-plugin-vmware_v1.0.11_x5.0_linux_amd64 plugin: 2024/07/17 15:22:51 vmrun path: /usr/bin/vmrun | |
2024/07/17 15:22:51 packer-plugin-vmware_v1.0.11_x5.0_linux_amd64 plugin: 2024/07/17 15:22:51 vdisk-manager path: /usr/bin/vmware-vdiskmanager | |
2024/07/17 15:22:51 packer-plugin-vmware_v1.0.11_x5.0_linux_amd64 plugin: 2024/07/17 15:22:51 Testing against vmware driver *common.Workstation10Driver, Success: false | |
2024/07/17 15:22:51 packer-plugin-vmware_v1.0.11_x5.0_linux_amd64 plugin: 2024/07/17 15:22:51 skipping *common.Workstation10Driver because it failed with the following error Workstation does not appear to be licensed. Please license it. | |
2024/07/17 15:22:51 packer-plugin-vmware_v1.0.11_x5.0_ |
I hereby claim:
- I am ssplatt on github.
- I am bretttaylor (https://keybase.io/bretttaylor) on keybase.
- I have a public key ASBNEkHP2WdKwCg5-kQAvWawWhI6ZrIL-Tz2bnV4DUEAZQo
To claim this, I am signing this object:
FROM debian:latest | |
WORKDIR /app | |
COPY docker-entrypoint.sh / | |
RUN apt-get update \ | |
&& apt-get upgrade -y \ | |
&& DEBIAN_FRONTEND=noninteractive apt-get install -y curl git bash zsh python3 \ | |
&& curl -fsSL https://deb.nodesource.com/setup_17.x | bash - \ | |
&& DEBIAN_FRONTEND=noninteractive apt-get install -y nodejs gcc g++ make yarn \ | |
&& chmod a+x /docker-entrypoint.sh | |
CMD [ "/docker-entrypoint.sh" ] |
This walkthrough is broken up into to parts: a quick-start guide to running Superalgos with Docker and a deeper, more theoretical dive into containers with the hopes of explaining some of the design decisions.
Superalgos, at its core, is a web application which also means it can be deployed inside a container like many other web applications. One of the leading platforms for operating containers is Docker. Docker can run on many different operatng systems and compute platforms. The containers provide an easy, fast, repeatable, and secure way to deploy and distribute applications. While it doesn't take much experience to run containers or Docker, there are some basics that any user should learn in order to use the technology effectively.
Before getting started, be aware that Docker is not the originally intended method of running the [Superalgos](https://github.com/Superalgos/S
--- | |
kind: ClusterRole | |
apiVersion: rbac.authorization.k8s.io/v1beta1 | |
metadata: | |
name: flannel | |
rules: | |
- apiGroups: | |
- "" | |
resources: | |
- pods |
sysbench --test=cpu --cpu-max-prime=20000 --num-threads=$(cat /proc/cpuinfo | grep processor | wc -l) run | |
sysbench 0.4.12: multi-threaded system evaluation benchmark | |
Running the test with following options: | |
Number of threads: 4 | |
Doing CPU performance benchmark | |
Threads started! | |
Done. |
on your odroid using the ubuntu-xenial image from hardkernel. for example, http://east.us.odroid.in/ubuntu_16.04lts/ubuntu64-16.04.3-minimal-odroid-c2-20171005.img.xz
apt install git docker.io
git clone https://github.com/docker/docker-ce
cd docker-ce
git checkout 17.12
apiVersion: extensions/v1beta1 | |
kind: DaemonSet | |
metadata: | |
creationTimestamp: null | |
generation: 1 | |
labels: | |
k8s-app: kube-proxy-amd64 | |
name: kube-proxy-amd64 | |
selfLink: /apis/extensions/v1beta1/namespaces/kube-system/daemonsets/kube-proxy-amd64 | |
namespace: kube-system |
context 'create npm resources' do | |
let(:facts) do | |
facts | |
end | |
let('nodejs::npm') do | |
{ | |
'myapp' => { | |
'ensure' => "present", | |
'target' => "/var/www/apps/myapp", | |
'use_package_json' => true |