OpenSCOW只能构建docker镜像吗？有没有方法编译成rpm包？

[wongkq]

如题目：
我们docker build的时候一直失败，有没有能将openscow编译成rpm包的方式？

[oct@manage OpenSCOW]$ docker build -f docker/Dockerfile.scow -t scow .
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
[1/3] STEP 1/2: FROM node:22-alpine@sha256:9bef0ef1e268f60627da9ba7d7605e8831d5b56ad07487d24d1aa386336d1944 AS base
Resolved "node" as an alias (/etc/containers/registries.conf.d/000-shortnames.conf)
Trying to pull docker.io/library/node@sha256:9bef0ef1e268f60627da9ba7d7605e8831d5b56ad07487d24d1aa386336d1944...
WARN[0181] Failed, retrying in 2s ... (1/3). Error: initializing source docker://node@sha256:9bef0ef1e268f60627da9ba7d7605e8831d5b56ad07487d24d1aa386336d1944: (Mirrors also failed: [dockerproxy.com/library/node@sha256:9bef0ef1e268f60627da9ba7d7605e8831d5b56ad07487d24d1aa386336d1944: pinging container registry dockerproxy.com: Get "https://dockerproxy.com/v2/": dial tcp 69.63.190.26:443: i/o timeout]
[registry.cn-hangzhou.aliyuncs.com/library/node@sha256:9bef0ef1e268f60627da9ba7d7605e8831d5b56ad07487d24d1aa386336d1944: reading manifest sha256:9bef0ef1e268f60627da9ba7d7605e8831d5b56ad07487d24d1aa386336d1944 in registry.cn-hangzhou.aliyuncs.com/library/node: requested access to the resource is denied]
[mirror.tencentyun.com/library/node@sha256:9bef0ef1e268f60627da9ba7d7605e8831d5b56ad07487d24d1aa386336d1944: pinging container registry mirror.tencentyun.com: Get "https://mirror.tencentyun.com/v2/": dial tcp: lookup mirror.tencentyun.com on 8.8.8.8:53: no such host]): docker.io/library/node@sha256:9bef0ef1e268f60627da9ba7d7605e8831d5b56ad07487d24d1aa386336d1944: pinging container registry registry-1.docker.io: Get "http://registry-1.docker.io/v2/": dial tcp 108.160.167.30:80: i/o timeout
WARN[0365] Failed, retrying in 2s ... (2/3). Error: initializing source docker://node@sha256:9bef0ef1e268f60627da9ba7d7605e8831d5b56ad07487d24d1aa386336d1944: (Mirrors also failed: [dockerproxy.com/library/node@sha256:9bef0ef1e268f60627da9ba7d7605e8831d5b56ad07487d24d1aa386336d1944: pinging container registry dockerproxy.com: Get "https://dockerproxy.com/v2/": dial tcp 103.252.114.11:443: i/o timeout]
[registry.cn-hangzhou.aliyuncs.com/library/node@sha256:9bef0ef1e268f60627da9ba7d7605e8831d5b56ad07487d24d1aa386336d1944: reading manifest sha256:9bef0ef1e268f60627da9ba7d7605e8831d5b56ad07487d24d1aa386336d1944 in registry.cn-hangzhou.aliyuncs.com/library/node: requested access to the resource is denied]
[mirror.tencentyun.com/library/node@sha256:9bef0ef1e268f60627da9ba7d7605e8831d5b56ad07487d24d1aa386336d1944: pinging container registry mirror.tencentyun.com: Get "https://mirror.tencentyun.com/v2/": dial tcp: lookup mirror.tencentyun.com on 8.8.8.8:53: no such host]): docker.io/library/node@sha256:9bef0ef1e268f60627da9ba7d7605e8831d5b56ad07487d24d1aa386336d1944: pinging container registry registry-1.docker.io: Get "http://registry-1.docker.io/v2/": dial tcp 199.59.149.231:80: i/o timeout
WARN[0548] Failed, retrying in 2s ... (3/3). Error: initializing source docker://node@sha256:9bef0ef1e268f60627da9ba7d7605e8831d5b56ad07487d24d1aa386336d1944: (Mirrors also failed: [dockerproxy.com/library/node@sha256:9bef0ef1e268f60627da9ba7d7605e8831d5b56ad07487d24d1aa386336d1944: pinging container registry dockerproxy.com: Get "https://dockerproxy.com/v2/": dial tcp 31.13.106.4:443: i/o timeout]
[registry.cn-hangzhou.aliyuncs.com/library/node@sha256:9bef0ef1e268f60627da9ba7d7605e8831d5b56ad07487d24d1aa386336d1944: reading manifest sha256:9bef0ef1e268f60627da9ba7d7605e8831d5b56ad07487d24d1aa386336d1944 in registry.cn-hangzhou.aliyuncs.com/library/node: requested access to the resource is denied]
[mirror.tencentyun.com/library/node@sha256:9bef0ef1e268f60627da9ba7d7605e8831d5b56ad07487d24d1aa386336d1944: pinging container registry mirror.tencentyun.com: Get "https://mirror.tencentyun.com/v2/": dial tcp: lookup mirror.tencentyun.com on 8.8.8.8:53: no such host]): docker.io/library/node@sha256:9bef0ef1e268f60627da9ba7d7605e8831d5b56ad07487d24d1aa386336d1944: pinging container registry registry-1.docker.io: Get "http://registry-1.docker.io/v2/": dial tcp 103.56.16.112:80: i/o timeout
Error: creating build container: initializing source docker://node@sha256:9bef0ef1e268f60627da9ba7d7605e8831d5b56ad07487d24d1aa386336d1944: (Mirrors also failed: [dockerproxy.com/library/node@sha256:9bef0ef1e268f60627da9ba7d7605e8831d5b56ad07487d24d1aa386336d1944: pinging container registry dockerproxy.com: Get "https://dockerproxy.com/v2/": dial tcp 185.60.216.50:443: i/o timeout]
[registry.cn-hangzhou.aliyuncs.com/library/node@sha256:9bef0ef1e268f60627da9ba7d7605e8831d5b56ad07487d24d1aa386336d1944: reading manifest sha256:9bef0ef1e268f60627da9ba7d7605e8831d5b56ad07487d24d1aa386336d1944 in registry.cn-hangzhou.aliyuncs.com/library/node: requested access to the resource is denied]
[mirror.tencentyun.com/library/node@sha256:9bef0ef1e268f60627da9ba7d7605e8831d5b56ad07487d24d1aa386336d1944: pinging container registry mirror.tencentyun.com: Get "https://mirror.tencentyun.com/v2/": dial tcp: lookup mirror.tencentyun.com on 8.8.8.8:53: no such host]): docker.io/library/node@sha256:9bef0ef1e268f60627da9ba7d7605e8831d5b56ad07487d24d1aa386336d1944: pinging container registry registry-1.docker.io: Get "http://registry-1.docker.io/v2/": dial tcp 114.43.24.59:80: i/o timeout