Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG: failed to mount: mounting "default-qbfp1r97" container "default-qbfp1r97": saving updated state for build container #4965

Open
jeven2016 opened this issue Aug 14, 2024 · 1 comment
Labels
kind/bug Something isn't working response-expired

Comments

@jeven2016
Copy link

jeven2016 commented Aug 14, 2024

Sealos Version

v4.3.5

How to reproduce the bug?

  1. create a sealos app for kubevirt's virtual machine
  2. locally import the sealos image
  3. execute 'sealos run ' command line for multiple times to create multiple VMs with different names

What is the expected behavior?

all 'sealos run' command lines completed and all VMs should be created successfully

What do you see instead?

one of the sealos pods failed to complete, the details as below:
[root@cluster-master-10 samples]# k logs -f sealosapp-vm-jg-209-predelete-26gfz -n vm-system

  • /tmp/ssh-init.sh
    ++ cat /tmp/sealosapp-ssh/hosts
  • export SEALOS_HOST=10.20.97.10
  • SEALOS_HOST=10.20.97.10
  • ssh -o StrictHostKeyChecking=no -i /root/.ssh/id_rsa [email protected] 'bash /opt/sealosapp/vm-jg-209/uninstall.sh'
    Warning: Permanently added '10.20.97.10' (ED25519) to the list of known hosts.
  • export COMMON_NAMESPACE=vm-system
  • COMMON_NAMESPACE=vm-system
  • export REPOSITORY=harbor.cloud.net
  • REPOSITORY=harbor.cloud.net
  • export TAG=v1.2.2
  • TAG=v1.2.2
  • export SEALOS_APP_LABELS=app.kubesphere.io/instance:sealosapp-vm-jg-20
  • SEALOS_APP_LABELS=app.kubesphere.io/instance:sealosapp-vm-jg-209
  • service_name=vm-jg-209
  • component=vm-app
  • '[' -z vm-jg-209 ']'
  • '[' -z vm-app ']'
  • sealos run harbor.cloud/vm-app:v1.2.2 -e NAMESPACE=vm-system -e UNINSTALL=true -e chart=vm-app -e release=vm-jg-209 -e CPU_CORES=4 -e DATA_DISK_1_PVC_VOLUME_MODE=Block -e DATA_DISK_1_SIZE=10Gi -e DATA_DISK_1_STORAGE_CLASS=sc-jnds-data -e DATA_DISK_1_TYPE=pvc -e DISK_SIZE=20Gi -e MEMORY=48Gi -e POWER_ON=true -e STORAGE_CLASS=sc-jnds-yw -e 'TCP_PORTS=22 5432 18198 18196 18089' --cmd=./opt/uninstall.sh -f
    2024-08-14T09:23:51 info sync new version copy pki config: /var/lib/sealos/data/default/pki /root/.sealos/default/pki
    2024-08-14T09:23:51 info sync new version copy etc config: /var/lib/sealos/data/default/etc /root/.sealos/default/etc
    2024-08-14T09:23:51 info start to install app in this cluster
    2024-08-14T09:23:51 info Executing SyncStatusAndCheck Pipeline in InstallProcessor
    2024-08-14T09:23:51 info Executing ConfirmOverrideApps Pipeline in InstallProcessor
    2024-08-14T09:23:51 info Executing PreProcess Pipeline in InstallProcessor
    Error: failed to mount: mounting "default-qbfp1r97" container "default-qbfp1r97": saving updated state for build container "0062981e675161ae37750216353d78f98db90a7be794d07751749bb050e7d02b": saving builder state to "/var/lib/containers/storage/overlay-containers/0062981e675161ae37750216353d78f98db90a7be794d07751749bb050e7d02b/userdata/buildah.json": rename /var/lib/containers/storage/overlay-containers/0062981e675161ae37750216353d78f98db90a7be794d07751749bb050e7d02b/userdata/.tmp-buildah.json1423736918 /var/lib/containers/storage/overlay-containers/0062981e675161ae37750216353d78f98db90a7be794d07751749bb050e7d02b/userdata/buildah.json: no such file or directory

Operating environment

- Sealos version: v4.3.5
- Docker version: 24.0.9
- Kubernetes version: 1.26
- Operating system:  openeuler 22.03
- Runtime environment:
- Cluster size:  standalone k3s cluster with only one node maintained
- Additional information:

Additional information

No response

@jeven2016 jeven2016 added the kind/bug Something isn't working label Aug 14, 2024
Copy link

stale bot commented Oct 16, 2024

This issue has been automatically closed because we haven't heard back for more than 60 days, please reopen this issue if necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working response-expired
Projects
None yet
Development

No branches or pull requests

1 participant