微信云托管官网
最新提问- 全部
- 文章
- 问答
- 全部
- 文章
- 问答
置顶C#服务器部署失败 cannot exec a container that has stoppe？
2024-09-14 18:10:08 check_eks_virtual_service : process, DescribeVersion_user_error_Exec lifecycle hook ([/bin/sh /app/cert/initenv.sh]) for Container "new2-002" in Pod "new2-002-74c9fcd6bd-5nhln_tiuaxlkk(be6a86f1-8c7f-4460-8f1e-4535a7283bea)" failed - error: rpc error: code = Unknown desc = failed to exec in container: failed to start exec "9a1e077e4671441d78ef218b6787c1fcbf611a7bfbf59876b857403ee1f25dc8": OCI runtime exec failed: exec failed: container_linux.go:370: starting container process caused: read init-p: connection reset by peer: unknown, message: "", [service]:[Exec lifecycle hook ([/bin/sh /app/cert/initenv.sh]) for Container "new2-002" in Pod "new2-002-74c9fcd6bd-5nhln_tiuaxlkk(be6a86f1-8c7f-4460-8f1e-4535a7283bea)" failed - error: rpc error: code = Unknown desc = failed to exec in container: failed to start exec "e09f80508bc5abfea2340be1ca3ab9621e9ac7dc39f62b8f036cafd24228a4e2": OCI runtime exec failed: exec failed: container_linux.go:370: starting container process caused: process_linux.go:103: executing setns process caused: exit status 1: unknown, message: "",Exec lifecycle hook ([/bin/sh /app/cert/initenv.sh]) for Container "new2-002" in Pod "new2-002-74c9fcd6bd-5nhln_tiuaxlkk(be6a86f1-8c7f-4460-8f1e-4535a7283bea)" failed - error: rpc error: code = Unknown desc = failed to exec in container: failed to start exec "966cfd74e3aca0a25d9e245226ae5503d0654ea31b18327dca0b0fdf6b7cad24": OCI runtime exec failed: exec failed: cannot exec a container that has stopped: unknown, message: "",Back-off restarting failed container,Exec lifecycle hook ([/bin/sh /app/cert/initenv.sh]) for Container "new2-002" in Pod "new2-002-74c9fcd6bd-5nhln_tiuaxlkk(be6a86f1-8c7f-4460-8f1e-4535a7283bea)" failed - error: rpc error: code = Unknown desc = failed to exec in container: failed to start exec "08d31bba6764e671598d8d90c0d958e8a10d78cd89ceb4590d2b5e6239e0fc1e": OCI runtime exec failed: exec failed: cannot exec a container that has stopped: unknown, message: "",Exec lifecycle hook ([/bin/sh /app/cert/initenv.sh]) for Container "new2-002" in Pod "new2-002-74c9fcd6bd-5nhln_tiuaxlkk(be6a86f1-8c7f-4460-8f1e-4535a7283bea)" failed - error: rpc error: code = Unknown desc = failed to exec in container: failed to start exec "c14845e0fa7a7a9401435c6333093f52fa5e1936fb13cacd8926eef16b4ba968": OCI runtime exec failed: exec failed: container_linux.go:370: starting container process caused: process_linux.go:103: executing setns process caused: exit status 1: unknown, message: "",Exec lifecycle hook ([/bin/sh /app/cert/initenv.sh]) for Container "new2-002" in Pod "new2-002-74c9fcd6bd-5nhln_tiuaxlkk(be6a86f1-8c7f-4460-8f1e-4535a7283bea)" failed - error: rpc error: code = Unknown desc = failed to exec in container: failed to start exec "cc17ee07d384f7c6fcc7b557c96668c7b16f599ed128acaca963aa976e15ffa2": OCI runtime exec failed: exec failed: container_linux.go:370: starting container process caused: process_linux.go:103: executing setns process caused: exit status 1: unknown, message: "",Exec lifecycle hook ([/bin/sh /app/cert/initenv.sh]) for Container "new2-002" in Pod "new2-002-74c9fcd6bd-5nhln_tiuaxlkk(be6a86f1-8c7f-4460-8f1e-4535a7283bea)" failed - error: rpc error: code = Unknown desc = failed to exec in container: failed to start exec "e38654ba14aaeff3c2b12424e848a8678b544df5ca5781de992a4fee9f91399b": OCI runtime exec failed: exec failed: container_linux.go:370: starting container process caused: read init-p: connection reset by peer: unknown, message: "",Exec lifecycle hook ([/bin/sh /app/cert/initenv.sh]) for Container "new2-002" in Pod "new2-002-74c9fcd6bd-5nhln_tiuaxlkk(be6a86f1-8c7f-4460-8f1e-4535a7283bea)" failed - error: rpc error: code = Unknown desc = failed to exec in container: failed to start exec "9a1e077e4671441d78ef218b6787c1fcbf611a7bfbf59876b857403ee1f25dc8": OCI runtime exec failed: exec failed: container_linux.go:370: starting container process caused: read init-p: connection reset by peer: unknown, message: "",]
09-14置顶大佬们可以直接修改云托管服务里的文件吗？每次修改都要重新部署吗
大佬们可以直接修改云托管服务里的文件吗？每次修改都要重新部署吗？发布成功的容器不支持上传文件吗？怎么停止服务的运行？为什么不支持修改和上传？
09-14置顶云托管怎么注销呢？
云托管怎么注销呢？
09-13置顶资源互联授权时出错，请问如何解决？
资源互联，授权的时候出错，请问如何解决。 如图： [图片]
09-12置顶云托管服务部署失败，没有明确的错误信息提示？
wx21950e87d8089690 prod-8gdm5hf624382dd4 tid=725965 rid=multi_tenant_1smxR3IiJVzvoi awaken bid=46212277 awaken-011 [图片]
09-07置顶为什么我从服务端发multipart/form-data时一直提示not well-formed？
如下是我组装post请求的代码： 我发现同样是是是用这个方法，当我上传一个.png文件的时候，就没有问题，但是当我上传一个.xlsx文件后，就反复失败，提示： The body of your POST request is not well-formed multipart/form-data. MalformedPOSTRequest在网上搜了相关资料，把MediaType.parse的内容改成了application/vnd.openxmlformats-officedocument.spreadsheetml.sheet之后也是一样的报错 public static String sendMultipartPost(String url, Map<String, String> body, File file, Map<String, String> headers) throws IOException { log.info("request url: {}, body: {}, headers: {}", url, body, headers); MultipartBody.Builder multipartBodyBuilder = new MultipartBody.Builder() .setType(MultipartBody.FORM) .addFormDataPart("file", file.getName(), RequestBody.create(MediaType.parse("multipart/form-data"), file)); if (body != null && !body.isEmpty()) { body.forEach(multipartBodyBuilder::addFormDataPart); } MultipartBody multipartBody = multipartBodyBuilder.build(); Request.Builder builder = new Request.Builder(); if (headers != null && !headers.isEmpty()) { headers.forEach(builder::addHeader); } Request request = builder .url(url) .post(multipartBody) .build(); try (Response response = client.newCall(request).execute()) { String responseBody = response.body().string(); log.info("the response body is: {}", responseBody); return responseBody; } }
09-06置顶golang程序云托管部署失败
golang程序多次部署失败，错误标识：wxab594dbca10bb77c prod-3g8cufp64532161d rid=multi_tenant_1smBTGtkqpUV66 golang-p5l2 ptid=505090 bid=46162259 golang-p5l2-005 部署方式选择的是基于官方模板，请问如何排查和处理？
09-05置顶微信云托管 CLI 工具上传问题如何处理？
× 代码包上传失败 Error [ERR_FR_MAX_BODY_LENGTH_EXCEEDED]: Request body larger than maxBodyLength limit Code: ERR_FR_MAX_BODY_LENGTH_EXCEEDED
09-05置顶部署springboot项目失败，说是ca-certificates证书问题，该怎么解决？
报错问题： WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping , message: "+ certFile=/app/cert/certificate.crt\n+ certLog=/app/cert.log\n+ srcIp=169.254.10.1\n+ srcHost=api.weixin.qq.com\n+ checkFileCnt=0\n+ is_user_root\n+ id -u\n+ '[' 0 -eq 0 ]\n+ echo 'User is root, patching env and certs.'\n+ '[' '!' -f /app/cert/certificate.crt ]\n+ '[' '!' -f /etc/os-release ]\n+ . /etc/os-release\n+ NAME='Alpine Linux'\n+ ID=alpine\n+ VERSION_ID=3.13.12\n+ PRETTY_NAME='Alpine Linux v3.13'\n+ HOME_URL=https://alpinelinux.org/\n+ BUG_REPORT_URL=https://bugs.alpinelinux.org/\n+ echo '[I]: os release is alpine'\n+ update-ca-certificates -h\nWARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping\n",Back-off restarting failed container,] 我的dockerfile代码 # 使用 HTTPS 协议访问容器云调用证书安装 RUN apk add ca-certificates
09-04置顶部分手机进行云托管网络请求后台无法正常取到参数？
wx.cloud.callContainer({ method:"POST", content_type:'application/x-www-form-urlencoded', data:{wx_code:code,userInfo:JSON.stringify(info)}, ）} 这样的格式请求服务端，大部分手机如华为、苹果手机基本正常，但是一部分手机如华为以前的安卓机，荣耀相关机型，小米等，感觉大部分问题出现在安卓上，这部分安卓机在以这种方式请求服务端时，无法正常获取参数，想弄清楚解决问题的方向
09-04置顶我用云托管，发现调试模式下才能展示数据，后面上线了一个，用了服务器，添加了服务器域名，数据还出不来？
体验模式数据没有？正式上线也没，该配的都配了
09-03置顶腾讯云服务器访问云托管对象存储不走内网？
我这边新购买了几台腾讯云服务器，但是在实际访问云托管中的对象存储文件速度很慢，实际下载速度只有3MB/s，但是同样在上海地区，这种情况不应该是走的内网吗？请问这种情况有没有配置方案可以解决的
08-29置顶部署失败，本地和个人服务器部署都没问题。以前部署也可以，这是什么原因?
部署开始于 2024-08-29 17:24:05 [1/2] 创建版本 失败 17s 创建版本失败：任务失败 [2024-08-29 17:24:12] Started by user coding [2024-08-29 17:24:12] Running in Durability level: MAX_SURVIVABILITY [2024-08-29 17:24:15] [Pipeline] Start of Pipeline [2024-08-29 17:24:16] [Pipeline] node [2024-08-29 17:24:16] Running on Jenkins in /root/workspace [2024-08-29 17:24:16] [Pipeline] { [2024-08-29 17:24:16] [Pipeline] stage [2024-08-29 17:24:16] [Pipeline] { (检出软件包) [2024-08-29 17:24:16] Stage "检出软件包" skipped due to when conditional [2024-08-29 17:24:16] [Pipeline] } [2024-08-29 17:24:16] [Pipeline] // stage [2024-08-29 17:24:17] [Pipeline] stage [2024-08-29 17:24:17] [Pipeline] { (检出 ZIP 包) [2024-08-29 17:24:17] Stage "检出 ZIP 包" skipped due to when conditional [2024-08-29 17:24:17] [Pipeline] } [2024-08-29 17:24:17] [Pipeline] // stage [2024-08-29 17:24:17] [Pipeline] stage [2024-08-29 17:24:17] [Pipeline] { (检出代码仓库) [2024-08-29 17:24:17] [Pipeline] sh [2024-08-29 17:24:17] + git clone ****** . [2024-08-29 17:24:17] Too many arguments. [2024-08-29 17:24:17] [2024-08-29 17:24:17] usage: git clone [<options>] [--] <repo> [<dir>] [2024-08-29 17:24:17] [2024-08-29 17:24:17] -v, --verbose be more verbose [2024-08-29 17:24:17] -q, --quiet be more quiet [2024-08-29 17:24:17] --progress force progress reporting [2024-08-29 17:24:17] -n, --no-checkout don't create a checkout [2024-08-29 17:24:17] --bare create a bare repository [2024-08-29 17:24:17] --mirror create a mirror repository (implies bare) [2024-08-29 17:24:17] -l, --local to clone from a local repository [2024-08-29 17:24:17] --no-hardlinks don't use local hardlinks, always copy [2024-08-29 17:24:17] -s, --shared setup as shared repository [2024-08-29 17:24:17] --recursive initialize submodules in the clone [2024-08-29 17:24:17] --recurse-submodules initialize submodules in the clone [2024-08-29 17:24:17] --template <template-directory> [2024-08-29 17:24:17] directory from which templates will be used [2024-08-29 17:24:17] --reference <repo> reference repository [2024-08-29 17:24:17] --dissociate use --reference only while cloning [2024-08-29 17:24:17] -o, --origin <name> use <name> instead of 'origin' to track upstream [2024-08-29 17:24:17] -b, --branch <branch> [2024-08-29 17:24:17] checkout <branch> instead of the remote's HEAD [2024-08-29 17:24:17] -u, --upload-pack <path> [2024-08-29 17:24:17] path to git-upload-pack on the remote [2024-08-29 17:24:17] --depth <depth> create a shallow clone of that depth [2024-08-29 17:24:17] --single-branch clone only one branch, HEAD or --branch [2024-08-29 17:24:17] --separate-git-dir <gitdir> [2024-08-29 17:24:17] separate git dir from working tree [2024-08-29 17:24:17] -c, --config <key=value> [2024-08-29 17:24:17] set config inside the new repository [2024-08-29 17:24:17] [2024-08-29 17:24:17] [Pipeline] } [2024-08-29 17:24:17] [Pipeline] // stage [2024-08-29 17:24:17] [Pipeline] stage [2024-08-29 17:24:17] [Pipeline] { (写入 dockerfile) [2024-08-29 17:24:17] Stage "写入 dockerfile" skipped due to earlier failure(s) [2024-08-29 17:24:17] [Pipeline] } [2024-08-29 17:24:17] [Pipeline] // stage [2024-08-29 17:24:17] [Pipeline] stage [2024-08-29 17:24:17] [Pipeline] { (构建 Docker 镜像) [2024-08-29 17:24:17] Stage "构建 Docker 镜像" skipped due to earlier failure(s) [2024-08-29 17:24:17] [Pipeline] } [2024-08-29 17:24:17] [Pipeline] // stage [2024-08-29 17:24:17] [Pipeline] stage [2024-08-29 17:24:18] [Pipeline] { (推送 Docker 镜像到 TCR) [2024-08-29 17:24:18] Stage "推送 Docker 镜像到 TCR" skipped due to earlier failure(s) [2024-08-29 17:24:18] [Pipeline] } [2024-08-29 17:24:18] [Pipeline] // stage [2024-08-29 17:24:18] [Pipeline] } [2024-08-29 17:24:18] [Pipeline] // node [2024-08-29 17:24:18] [Pipeline] End of Pipeline [2024-08-29 17:24:18] ERROR: script returned exit code 129 [2024-08-29 17:24:18] Finished: FAILURE *** -----------构建xmspringboot-013----------- 2024-08-29 17:24:11 create_build_image : succ,
08-29置顶如何修改对象存储、静态资源存储文件名称呢？现在没有选项可以改名，只有删除
如何修改对象存储、静态资源存储文件名称呢？现在没有选项可以改名，只有删除 [图片]
08-29置顶微信云托管部署成功但是访问接口还是旧的代码返回的结果？
[图片] 仓库已经注销了这段代码了，但是返回的还是注销的代码返回的结果[图片] 是还没更新完全吗，需要等多久
08-29置顶云托管服务中使用callContainer方法，目前AI生成图片较慢，超出15秒才能返回结果，何解
https://developers.weixin.qq.com/miniprogram/dev/wxcloud/reference-sdk-api/container/Cloud.callContainer.html [图片] 如标题所述问题，此处文档中的timeout为15秒，在上述场景中，AI模型在15秒内并为返回图片结果，是否会出现图片还未返回，但请求已超时的问题呢？ 针对此种需求，有解决办法吗？
08-28置顶首次部署YOLOv5项目，镜像构建一直超时，怎么才能优化到规定时间内？
本地可以构建成功，每次到云托管上面就会出现下面的日志： [图片] 提工单问了客服说是我构建时间太长了，本人技术有限实在优化不了了。请大家帮帮忙 # 使用官方Python运行时作为父镜像 FROM python:3.11 RUN apt-get update && apt-get install -y libgl1-mesa-glx # 设定当前的工作目录 WORKDIR /app COPY requirements.txt ./ # 安装requirements.txt中指定的所有依赖 RUN pip config set global.index-url http://mirrors.cloud.tencent.com/pypi/simple \ && pip config set global.trusted-host mirrors.cloud.tencent.com \ && pip install --upgrade pip \ && pip install --user -r requirements.txt \ && pip install opencv-python \ && pip install opencv-python-headless # 拷贝当前项目到/app目录下（.dockerignore中文件除外） COPY . ./ # 使端口80对外部可用，用于Web服务 EXPOSE 5000 # 当容器启动时运行app.py CMD ["python3", "./flaskApi.py", "0.0.0.0", "5000"]]
08-27置顶微信云托管
做以图搜图的小程序，只对接百度云的图像搜索技术，可以用微信云托管吗
08-26置顶云托管的websocket 开通外网访问,小程序配置合法域名无法使用, 怎么解决?
[图片]
08-22置顶wx.cloud.connectContainer无法连接后端websocket
https://developers.weixin.qq.com/minigame/dev/wxcloudrun/src/ 问题：wx.cloud.connectContainer无法连接后端websocket，请求网址为'wss://express-u811-prod-xxx-xxx.ap-xxx.run.wxcloudrun.com/ws'，报错1006，都没请求到后端。 容器启动绑定端口27082：27081。直接请求ws://127.0.0.1:27081/ws，是能建立连接的。 代码：用的是官方示例 客户端 export const websocketTest = async (flag) => { const { socketTask } = await wx.cloud.connectContainer({ config: { env: env, }, service: server_name, // 替换自己的服务名 path: '/ws' }) socketTask.onMessage(function (res) { console.log(flag, '【WEBSOCKET】', res.data) }) socketTask.onOpen(async function (res) { console.log(flag,'【WEBSOCKET】', '链接成功！', res) socketTask.send({ data: '这是小程序消息' }) }) socketTask.onClose(async function (err) { console.log(flag,'【WEBSOCKET】链接关闭！') console.log(err) }) return socketTask } websocketTest('1') websocketTest('2') // 故意多发起一次链接 node后端 const application = express(); const {app} = expressWS(application) const connect = {} app.ws('/ws', function (ws, req) { let openid = req.headers['x-wx-openid'] // 从header中获取用户openid信息 if (openid == null) { // 如果不存在则不是微信侧发起的 openid = new Date().getTime() // 使用时间戳代替 } if (connect[openid] != null) { // 判断用户是否有连接 ws.send('当前用户已经在其他设备连接过，无法重复连接') // 发送重复连接信息 ws.close() // 关闭连接 } else { connect[openid] = { // 记录用户信息 openid: openid, // 用户openid source: req.headers['x-wx-source'] || '非微信', // 用户微信来源 unionid: req.headers['x-wx-unionid'] || '-', // 用户unionid ip: req.headers['x-forwarded-for'] || '未知' // 用户所在ip地址 } console.log('链接请求头信息', req.headers) ws.on('message', function (msg) { console.log('收到消息：', msg) ws.send(`收到-${msg}`) }) ws.on('error', function(error) { console.error('WebSocket连接错误：', error); }); ws.on('close', function (code, reason) { console.log('链接断开：', openid, code, reason.toString('utf-8')) delete connect[openid] }) console.log("end....") } })
08-21
不建议修改。如果有需要修改的文件，还是放云存储吧