freedomofpress
Issue with Docker Desktop on Mac
What happened?
I have deleted Docker Desktop and the previous version of Dangerzone. Then I reinstalled Docker Desktop (from their website) following the steps from Dangerzone 0.8.1. However, Docker Desktop doesn't let me log in (as I previously had, with my personal GitHub account) and instead, it says this:
Sign in to continue using Docker Desktop. Membership in the [my company] organization is required.
Previously to deleting Docker, everything was working fine (I had just used the tool yesterday). Is there solution to this? I am on a company-managed device, but it should be possible to use Dangerzone without having to pay/request a Docker account from my organisation.
operating system version
MacOS Sequoia 15.1.1
Processor type
Apple Silicon
Dangerzone version
0.8.1
Docker info
Client:
Version: 27.4.0
API version: 1.47
Go version: go1.22.10
Git commit: bde2b89
Built: Sat Dec 7 10:35:43 2024
OS/Arch: darwin/arm64
Context: desktop-linux
Server: Docker Desktop 4.37.1 (178610)
Engine:
Version: 27.4.0
API version: 1.47 (minimum version 1.24)
Go version: go1.22.10
Git commit: 92a8393
Built: Sat Dec 7 10:38:33 2024
OS/Arch: linux/arm64
Experimental: false
containerd:
Version: 1.7.21
GitCommit: 472731909fa34bd7bc9c087e4c27943f9835f111
runc:
Version: 1.1.13
GitCommit: v1.1.13-0-g58aa920
docker-init:
Version: 0.19.0
GitCommit: de40ad0
docker images
Error response from daemon: Sign-in enforcement is enabled. Open Docker Desktop and sign in to a Docker account associated with your organization(s), or contact your administrators if this is unexpected.
Document conversion logs
No response
Additional info
No response
Yikes, sorry for this. I haven't encountered such an issue before, but from what I see in the docs, this looks like something that your company's admin would potentially configure in your laptop. If they haven't done this, then it may very well be a Docker bug (it has happened before).
I don't have a definitive solution I'm afraid, other than checking your laptop for the presence of files that would enforce the sign-in, contacting your company's admin, or filing a bug in Docker's issue tracker. In the long term, we want to ditch Docker altogether and go with Podman Desktop (https://github.com/freedomofpress/dangerzone/issues/925), but we're not there yet.
Resolved as part of #1225, which will be soon pushed to main. We are no longer relying on Docker Desktop and we'll be using Podman internally, without need for user interaction.
Thank you! So I should just wait until the next version (0.9.2), right? Or can I test it already?
Yeah, I'm afraid you'll need to wait a tad bit until we release 0.10.0, since it's a rather big shift. We'll probably do an open beta before the actual release, and invite existing users to test it out. We'll update our news section soon, and we'll announce something on GitHub / Mastodon as well.