CNI_PLUGIN_VERSION="v1.7.1"CNI_PLUGIN_TAR="cni-plugins-linux-amd64-$CNI_PLUGIN_VERSION.tgz"# change arch if not on amd64CNI_PLUGIN_INSTALL_DIR="/opt/cni/bin"curl-LO"https://github.com/containernetworking/plugins/releases/download/$CNI_PLUGIN_VERSION/$CNI_PLUGIN_TAR"sudo mkdir -p"$CNI_PLUGIN_INSTALL_DIR"sudo tar -xf"$CNI_PLUGIN_TAR"-C"$CNI_PLUGIN_INSTALL_DIR"rm"$CNI_PLUGIN_TAR"
crictl
DOWNLOAD_DIR="/usr/local/bin"sudo mkdir -p"$DOWNLOAD_DIR"CRICTL_VERSION="v1.33.0"ARCH="amd64"curl-L"https://github.com/kubernetes-sigs/cri-tools/releases/download/${CRICTL_VERSION}/crictl-${CRICTL_VERSION}-linux-${ARCH}.tar.gz"|sudo tar -C$DOWNLOAD_DIR-xz
mikoto@kubernetes:~$ sudo kubectl get nodesNAME STATUS ROLES AGE VERSIONkubernetes Ready control-plane 7m51s v1.33.1mikoto@kubernetes:~$ sudo kubectl run hello-world --image=hello-world --restart=Neverpod/hello-world createdmikoto@kubernetes:~$ sudo kubectl get podNAME READY STATUS RESTARTS AGEhello-world 0/1 Completed 0 23smikoto@kubernetes:~$ sudo kubectl logs pod/hello-worldHello from Docker!This message shows that your installation appears to be working correctly.To generate this message, Docker took the following steps:1. The Docker client contacted the Docker daemon.2. The Docker daemon pulled the "hello-world" image from the Docker Hub.(amd64)3. The Docker daemon created a new container from that image which runs theexecutable that produces the output you are currently reading.4. The Docker daemon streamed that output to the Docker client, which sent itto your terminal.To try something more ambitious, you can run an Ubuntu container with:$ docker run -it ubuntu bashShare images, automate workflows, and more with a free Docker ID:https://hub.docker.com/For more examples and ideas, visit:https://docs.docker.com/get-started/
mikoto@kubernetes:~$ sudo docker run -it--rm hello-worldHello from Docker!This message shows that your installation appears to be working correctly.To generate this message, Docker took the following steps:1. The Docker client contacted the Docker daemon.2. The Docker daemon pulled the "hello-world" image from the Docker Hub.(amd64)3. The Docker daemon created a new container from that image which runs theexecutable that produces the output you are currently reading.4. The Docker daemon streamed that output to the Docker client, which sent itto your terminal.To try something more ambitious, you can run an Ubuntu container with:$ docker run -it ubuntu bashShare images, automate workflows, and more with a free Docker ID:https://hub.docker.com/For more examples and ideas, visit:https://docs.docker.com/get-started/
diff --git a/assembly/assembly-wsmaster-war/src/main/webapp/WEB-INF/classes/che/che.properties b/assembly/assembly-wsmaster-war/src/main/webapp/WEB-INF/classes/che/che.propertiesindex b9c8358..0e008fa 100644--- a/assembly/assembly-wsmaster-war/src/main/webapp/WEB-INF/classes/che/che.properties+++ b/assembly/assembly-wsmaster-war/src/main/webapp/WEB-INF/classes/che/che.properties@@ -560,13 +560,13 @@ che.infra.openshift.project.init_with_server_sa=true # Docker image of {prod-short} plugin broker app that resolves workspace tools configuration and copies plugins dependencies to a workspace. # The {prod-short} Operator overrides these images by default. Changing the images here will not # have an effect if {prod-short} is installed using the Operator.-che.workspace.plugin_broker.metadata.image=quay.io/eclipse/che-plugin-metadata-broker:v3.4.0+che.workspace.plugin_broker.metadata.image=mikoto2000/che-plugin-metadata-broker:arm64 # Docker image of Che plugin artifacts broker. # This broker runs as an init container on the workspace Pod. Its job is to take in a list of plugin identifiers # (either references to a plugin in the registry or a link to a plugin meta.yaml) and ensure that the correct .vsix # and .theia extensions are downloaded into the /plugins directory, for each plugin requested for the workspace.-che.workspace.plugin_broker.artifacts.image=quay.io/eclipse/che-plugin-artifacts-broker:v3.4.0+che.workspace.plugin_broker.artifacts.image=mikoto2000/che-plugin-artifacts-broker:arm64 # Configures the default behavior of the plugin brokers when provisioning plugins into a workspace. # If set to true, the plugin brokers will attempt to merge plugins when possible: they run in
Maven プロジェクトのビルド
Che Multiuser :: PostgreSQL Tck
で失敗するため、動作に必要なモジュールを別途個別にビルドしている。