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: Failed to restart autofs.service #85

Closed
joshkrz opened this issue Sep 18, 2022 · 6 comments
Closed

MacOS: Failed to restart autofs.service #85

joshkrz opened this issue Sep 18, 2022 · 6 comments

Comments

@joshkrz
Copy link

joshkrz commented Sep 18, 2022

When installing Decks dependencies on the "All set & Done" step it fails and stops with: Failed to restart autofs.service: Unit autofs.service not found..

Intel based MacOS Montery 12.5.1 with Deck 4.2.0.

Edit: After restarting deck it seems to boot up fine. I haven't tested spinning up any containers.

Edit 2: Attempting to spin up a container keeps asking Grant Full Disk Access to "nfsd" even though it already has this permission. Resarting Deck has no effect.

@presswizards
Copy link

presswizards commented Sep 19, 2022

'Grant Full Disk Access to "nfsd"' keeps coming up for me too even after already adding it to Full Disk Access. I've restarted Deck, rebooted, etc. Mac Studio M1 Max on Monterey 12.6 with Deck 4.2.0.

@sfx101
Copy link
Owner

sfx101 commented Sep 19, 2022

Hi,
Could you please do the following?

  1. Open the deck app and go to setting, click on Docker engine & uncheck Remote engine

image

  1. Uninstall multipass using sudo sh "/Library/Application Support/com.canonical.multipass/uninstall.sh"
  2. Restart deck app

The above should reinstall correctly, there might have been an issue while installing previously which we'll find out and fix.

@presswizards
Copy link

@sfx101 I unchecked remote engine, uninstalled, and then restarted Deck, and tried to create a new project. It still prompted for NFSD. I went to settings and unchecked remote engine again, then tried to create a new project, and it worked, but would not start. So I checked remote engine, and then it would start.

@presswizards
Copy link

@sfx101 Had to do the same thing, uncheck and add project, then recheck it to start, to create another WordPress project, but then both would get Can't connect to database errors every other page load, and that wasn't very usable at all then.

@nabad600
Copy link
Collaborator

Hi @presswizards, Thank you for reply, can you check link
https://www.loom.com/share/613e880063dc43fcba9a0869aa1aecab
Appreciate your feedback here.

@nabad600
Copy link
Collaborator

nabad600 commented Mar 6, 2023

Hi All,
We may need to close this ticket in the next 24 hours. So, I request you to inform us about the status of your query.
Let us know of any issues, we'd be happy to help.

@nabad600 nabad600 closed this as completed Mar 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants