alpine/curlIf enjoy, please consider buying me a coffee.
Alpine-based image with just curl
NOTES: the original upstream [***] is in read-only (archived statue), its images used base image of alpine:3.7, and are 4 years old now, vulnerabilities in its image, which is risk to use it.
This repo will manage with latest alpine version, and passed trivy scan.
If you need HTTP/3 supported, please use another image alpine/curl-http3 at [***]
docker runconsole$ docker run --rm alpine/curl -fsSL [***]
Or use it as alias command
alias curl="docker run --rm alpine/curl" curl -fsSL [***]
kubectl run# Each execution typically takes approximately 5 to 10 seconds due to the need to pull the image and create the pod. kubectl run curl --rm -it --image=alpine/curl -- -fsSL [***] # if you want to test the service within kubernetes cluster, $ kubectl get service # suppose, "productpage" is the service name, and "9080" is the service port # productpage ClusterIP 10.99.117.108 <none> 9080/TCP 123m kubectl run curl --rm -it --image=alpine/curl -- -sS productpage.default:9080/index.html
There is a rare case, that your kubernetes has istio auto injection (or similar sidecar solution) set as true, pod or containers start with network issue if istio-proxy (the sidecar) is not ready. So we need add extra option to reject that setting.
kubectl run curl --rm -it --overrides='{ "apiVersion": "v1", "metadata": { "labels": { "sidecar.istio.io/inject": "false" } } }' --image=alpine/curl -- -sS productpage.default:9080/productpage
or use it as alias command
alias kubecurl="kubectl run curl --rm -it --image=alpine/curl --" kubecurl -fsSL [***]
alpine/curl:8.1.2: based on curl versionThe image is passed the trivy scan, you can run command to confirm
$ docker run --rm -v /var/run/docker.sock:/var/run/docker.sock \ -v $HOME/Library/Caches:/root/.cache/ aquasec/trivy image alpine/curl ... ================================ Total: 0 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 0, CRITICAL: 0)

探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
在 Linux 系统配置镜像服务
在 Docker Desktop 配置镜像
Docker Compose 项目配置
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
在宝塔面板一键配置镜像
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 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。
来自真实用户的反馈,见证轩辕镜像的优质服务