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

MacOS reboot remote machine cause lost mount volume #13768

Closed
hyche opened this issue Apr 4, 2022 · 20 comments
Closed

MacOS reboot remote machine cause lost mount volume #13768

hyche opened this issue Apr 4, 2022 · 20 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. machine macos MacOS (OSX) related remote Problem is in podman-remote

Comments

@hyche
Copy link

hyche commented Apr 4, 2022

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description
Lost mount volume when machine is rebooted.

Steps to reproduce the issue:

  1. Init machine with mount volume: podman machine init --cpus 2 --disk-size 30 -m 2048 --now -v $HOME:/mnt/Users/me

  2. ssh to machine with podman machine ssh then execute sudo reboot

  3. Lost data inside mounted folder /mnt/Users/me

Describe the results you received:
empty folder /mnt/Users/me

Describe the results you expected:
Still have data after rebooting

Additional information you deem important (e.g. issue happens only occasionally):

Output of podman version:

Client:       Podman Engine
Version:      4.0.0-dev
API Version:  4.0.0-dev
Go Version:   go1.18
Git Commit:   aecb2023d240b69690f35721efcee7d724eba3f5-dirty
Built:        Mon Apr  4 21:47:27 2022
OS/Arch:      darwin/arm64

Server:       Podman Engine
Version:      4.0.2
API Version:  4.0.2
Go Version:   go1.16.14
Built:        Thu Mar  3 21:58:50 2022
OS/Arch:      linux/arm64

Output of podman info --debug:

host:
  arch: arm64
  buildahVersion: 1.24.1
  cgroupControllers:
  - memory
  - pids
  cgroupManager: systemd
  cgroupVersion: v2
  conmon:
    package: conmon-2.1.0-2.fc35.aarch64
    path: /usr/bin/conmon
    version: 'conmon version 2.1.0, commit: '
  cpus: 2
  distribution:
    distribution: fedora
    variant: coreos
    version: "35"
  eventLogger: journald
  hostname: localhost.localdomain
  idMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 1000000
    uidmap:
    - container_id: 0
      host_id: 501
      size: 1
    - container_id: 1
      host_id: 100000
      size: 1000000
  kernel: 5.15.18-200.fc35.aarch64
  linkmode: dynamic
  logDriver: journald
  memFree: 1669873664
  memTotal: 2048114688
  networkBackend: netavark
  ociRuntime:
    name: crun
    package: crun-1.4.2-1.fc35.aarch64
    path: /usr/bin/crun
    version: |-
      crun version 1.4.2
      commit: f6fbc8f840df1a414f31a60953ae514fa497c748
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +YAJL
  os: linux
  remoteSocket:
    exists: true
    path: /run/user/501/podman/podman.sock
  security:
    apparmorEnabled: false
    capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
    rootless: true
    seccompEnabled: true
    seccompProfilePath: /usr/share/containers/seccomp.json
    selinuxEnabled: true
  serviceIsRemote: true
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: slirp4netns-1.1.12-2.fc35.aarch64
    version: |-
      slirp4netns version 1.1.12
      commit: 7a104a101aa3278a2152351a082a6df71f57c9a3
      libslirp: 4.6.1
      SLIRP_CONFIG_VERSION_MAX: 3
      libseccomp: 2.5.3
  swapFree: 0
  swapTotal: 0
  uptime: 2m 11.38s
plugins:
  log:
  - k8s-file
  - none
  - passthrough
  - journald
  network:
  - bridge
  - macvlan
  volume:
  - local
registries:
  search:
  - docker.io
store:
  configFile: /var/home/core/.config/containers/storage.conf
  containerStore:
    number: 0
    paused: 0
    running: 0
    stopped: 0
  graphDriverName: overlay
  graphOptions: {}
  graphRoot: /var/home/core/.local/share/containers/storage
  graphStatus:
    Backing Filesystem: xfs
    Native Overlay Diff: "true"
    Supports d_type: "true"
    Using metacopy: "false"
  imageCopyTmpDir: /var/tmp
  imageStore:
    number: 0
  runRoot: /run/user/501/containers
  volumePath: /var/home/core/.local/share/containers/storage/volumes
version:
  APIVersion: 4.0.2
  Built: 1646319530
  BuiltTime: Thu Mar  3 21:58:50 2022
  GitCommit: ""
  GoVersion: go1.16.14
  Os: ""
  OsArch: linux/arm64
  Version: 4.0.2

Package info (e.g. output of rpm -q podman or apt list podman):

Output of brew info podman

podman: stable 4.0.3 (bottled), HEAD
Tool for managing OCI containers and pods
https://podman.io/
/opt/homebrew/Cellar/podman/HEAD-aecb202 (173 files, 46.3MB) *
  Built from source on 2022-04-05 at 00:12:57
/opt/homebrew/Cellar/podman/4.0.2 (172 files, 47.9MB)
  Poured from bottle on 2022-03-22 at 03:16:23
From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/podman.rb
License: Apache-2.0
==> Dependencies
Build: go ✔, go-md2man ✔
Required: qemu ✔
==> Options
--HEAD
	Install HEAD version
==> Caveats
fish completions have been installed to:
  /opt/homebrew/share/fish/vendor_completions.d
==> Analytics
install: 18,761 (30 days), 45,865 (90 days), 116,581 (365 days)
install-on-request: 18,754 (30 days), 45,845 (90 days), 116,557 (365 days)
build-error: 9 (30 days)

Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)

Yes

Additional environment details (AWS, VirtualBox, physical, etc.):

@openshift-ci openshift-ci bot added the kind/bug Categorizes issue or PR as related to a bug. label Apr 4, 2022
@github-actions github-actions bot added macos MacOS (OSX) related remote Problem is in podman-remote labels Apr 4, 2022
@mheon
Copy link
Member

mheon commented Apr 4, 2022

@baude PTAL

@Luap99 Luap99 added the machine label Apr 4, 2022
@baude
Copy link
Member

baude commented Apr 5, 2022

this is a known problem. the work around is to issue a podman machine stop and then a podman machine start. do not use power control from within the vm.

@baude
Copy link
Member

baude commented Apr 5, 2022

@rhatdan @ashley-cui would either of you want to see if we can move this to a service? like a proof of concept?

@github-actions
Copy link

github-actions bot commented May 6, 2022

A friendly reminder that this issue had no activity for 30 days.

@rhatdan
Copy link
Member

rhatdan commented May 6, 2022

@baude did you add the ability to mount volumes after the fact? If so could we realize on the MAC that the machine is rebooted and trigger an event to remount volumes?

@baude
Copy link
Member

baude commented May 6, 2022

I have not added it yet. And no I don't think so.

@github-actions
Copy link

github-actions bot commented Jun 6, 2022

A friendly reminder that this issue had no activity for 30 days.

@rhatdan
Copy link
Member

rhatdan commented Jun 6, 2022

@baude @ashley-cui Any progress on this?

@baude
Copy link
Member

baude commented Jun 6, 2022

no, and I dont have a good way to solve this. It will require some more research.

@github-actions
Copy link

github-actions bot commented Jul 7, 2022

A friendly reminder that this issue had no activity for 30 days.

@rhatdan
Copy link
Member

rhatdan commented Jul 7, 2022

@gbraad Any ideas on this?

@gbraad
Copy link
Member

gbraad commented Jul 7, 2022

For minishift we always wrote the mount info in the rc.local file to persist across reboots or hangs of the VM.

@rhatdan
Copy link
Member

rhatdan commented Jul 7, 2022

@baude @ashley-cui thoughts

@github-actions
Copy link

github-actions bot commented Aug 7, 2022

A friendly reminder that this issue had no activity for 30 days.

@rhatdan
Copy link
Member

rhatdan commented Aug 7, 2022

@baude @ashley-cui thoughts

@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@schamane
Copy link

I have same issue, lost my /Users volume just after podman machine stop and than start...

@davemaul
Copy link

davemaul commented Feb 6, 2023

Same here. Is there any idea why this is happening?

@riskersen
Copy link

This issue is still alive

@Luap99
Copy link
Member

Luap99 commented Jul 17, 2023

This looks like a duplicate of #15976 which has more information so I am closing this.

@Luap99 Luap99 closed this as completed Jul 17, 2023
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Oct 16, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 16, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. machine macos MacOS (OSX) related remote Problem is in podman-remote
Projects
None yet
Development

No branches or pull requests

9 participants