microej/sdk!SDK 5.9 Compatible !SDK 5.8 Compatible !SDK 5.7 Compatible !SDK 5.6 Compatible !SDK 5.5 Compatible !SDK 5.4 Compatible !SDK 4.1 Compatible
This is the git repository to build the MicroEJ BuildKit Docker Image for various MicroEJ SDK versions.
All images referenced in this document are available in our Docker Hub repository. You can also build them yourself following build instruction bellow and our Github repository.
Since SDK version 5.6.2 the SDK has been available in 2 versions: JDK 8 and JDK 11. The JDK11 image is suffixed with -jdk11. The image tagged lastest is version 5.9.0-jdk11.
5.4.1 and aboveFor MicroEJ SDK version 5.4.1 and above, please refer to
<[***]>.
The use of the SDK Docker images requires to approve the End-User License Agreement.
You can accept the EULA by setting the ACCEPT_MICROEJ_SDK_EULA_XXX environment variable to YES,
whereis XXX is the version of the EULA version, for example ACCEPT_MICROEJ_SDK_EULA_V3_1B=YES.
Start the image for interactive usage:
console$ docker run --rm -it -e ACCEPT_MICROEJ_SDK_EULA_V3_1B=YES microej/sdk:5.8.1 bash
Build a project from a local folder:
console$ docker run --rm -v PATH/TO/PROJECT:/project -w /project -e ACCEPT_MICROEJ_SDK_EULA_V3_1B=YES microej/sdk:5.8.1 mmm build
You can also build the image yourself from the Dockerfile.
This requires to:
[***] and the SDK version is 23.07, the SDK Distribution should be uploaded at [***].SDK_DISTRIBUTION_BASE_URL argument:console$ docker build --build-arg="SDK_DISTRIBUTION_BASE_URL=[***]" -t microej/sdk:5.8.1 5.8.1
4.1.5 to 5.3.1For MicroEJ SDK version 4.1.5 to 5.3.1, please refer to
<[***]>.
Start the image for interactive usage:
console$ docker run --rm -it microej/sdk:4.1.5 bash
Build a project from a local folder:
console$ docker run --rm -v PATH/TO/PROJECT:/project -w /project microej/sdk:4.1.5 build_module_local.sh ./
You can also build the image yourself from Dockerfile:
console$ docker build -t microej/sdk:4.1.5 4.1.5
A Jenkinsfile is at the root of this project to automatically test project Dockerfiles. You can launch it using Jenkins CI.
We followed the Jenkins recommendations to write this Jenkinsfile : Using Docker with Pipeline.
If you want to run it, you need to have at least one node labelled docker.
You can either :
Add your custom CA certificate to the docker image by adding these lines
to the Dockerfile you want to build :
consoleUSER root COPY company.cer $JAVA_HOME/jre/lib/security RUN \ cd $JAVA_HOME/jre/lib/security \ && keytool -keystore cacerts -storepass changeit -noprompt -trustcacerts -importcert -alias companycert -file company.cer
Mount your keystore using -v in the docker container and use it with mmm
by adding -Djavax.net.ssl.trustStore=keystore_path_in_container to
your build
The recommended way to do that is to mount your ivysettings into your
docker container and use MMM-CLI with parameter -r to specify the
module repository settings file location.
Please refer to MicroEJ Module Manager documentation for more information.
Markdown
Copyright 2021-2024 MicroEJ Corp. All rights reserved.
Use of this source code is governed by a BSD-style license that can be found with this software.
探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
在 Linux 系统配置镜像服务
在 Docker Desktop 配置镜像
Docker Compose 项目配置
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
VS Code Dev Containers 配置
MacOS OrbStack 容器配置
在宝塔面板一键配置镜像
Synology 群晖 NAS 配置
飞牛 fnOS 系统配置镜像
极空间 NAS 系统配置服务
爱快 iKuai 路由系统配置
绿联 NAS 系统配置镜像
QNAP 威联通 NAS 配置
Podman 容器引擎配置
HPC 科学计算容器配置
ghcr、Quay、nvcr 等镜像仓库
无需登录使用专属域名
需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
免费版仅支持 Docker Hub 访问,不承诺可用性和速度;专业版支持更多镜像源,保证可用性和稳定速度,提供优先客服响应。
专业版支持 docker.io、gcr.io、ghcr.io、registry.k8s.io、nvcr.io、quay.io、mcr.microsoft.com、docker.elastic.co 等;免费版仅支持 docker.io。
当返回 402 Payment Required 错误时,表示流量已耗尽,需要充值流量包以恢复服务。
通常由 Docker 版本过低导致,需要升级到 20.x 或更高版本以支持 V2 协议。
先检查 Docker 版本,版本过低则升级;版本正常则验证镜像信息是否正确。
使用 docker tag 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。
来自真实用户的反馈,见证轩辕镜像的优质服务