Cannot create any workspaces

[dhirjgupta]

Describe the bug
Git clone step fails when creating a workspace, even for sample projects

To Reproduce
Steps to reproduce the behavior:
2. set local Docker as provider / target
3. run daytona create
4. select a sample project
5. Docker / Local

Expected behavior
Creates a workspace

Screenshots

Desktop (please complete the following information):

• Mac M3 Apple Silicon Chip
• Daytona Version: 0.50.0

**Additional Context
I've tried running with sudo daytona as well with the same results

[Tpuljak]

@dhirjgupta did you maybe run the daytona server with sudo?

[dhirjgupta]

Hi @Tpuljak - no. The only sudo used throughout the process was the one instance mentioned in the install command:
curl -sfL https://download.daytona.io/daytona/install.sh | sudo bash && daytona server -y && daytona

I tried uninstalling and reinstalling a few times using all three methods:

• installation script
• binary
• brew

[Tpuljak]

What's the result of:

1. ps aux | grep daytona
2. docker info

[dhirjgupta]

@Tpuljak - results below

$ ps aux | grep daytona
dude              9760   1.9  0.0 410742528   1584 s036  S+    6:45PM   0:00.01 grep daytona
root              2765   0.0  0.0 411867056  13088   ??  S    Tue06PM   0:40.02 /Users/dude/Library/Application Support/daytona/providers/docker-provider/docker-provider
root               988   0.0  0.2 412264112  87776   ??  Ss   Tue06PM  20:06.80 /usr/local/bin/daytona daemon-serve

$ docker info
Client:
 Version:    27.3.1
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  ai: Ask Gordon - Docker Agent (Docker Inc.)
    Version:  v0.1.0
    Path:     /Users/dude/.docker/cli-plugins/docker-ai
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.18.0-desktop.2
    Path:     /Users/dude/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.30.3-desktop.1
    Path:     /Users/dude/.docker/cli-plugins/docker-compose
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.37
    Path:     /Users/dude/.docker/cli-plugins/docker-debug
  desktop: Docker Desktop commands (Alpha) (Docker Inc.)
    Version:  v0.0.15
    Path:     /Users/dude/.docker/cli-plugins/docker-desktop
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.2
    Path:     /Users/dude/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.27
    Path:     /Users/dude/.docker/cli-plugins/docker-extension
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.5
    Path:     /Users/dude/.docker/cli-plugins/docker-feedback
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.4.0
    Path:     /Users/dude/.docker/cli-plugins/docker-init
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     /Users/dude/.docker/cli-plugins/docker-sbom
  scout: Docker Scout (Docker Inc.)
    Version:  v1.15.0
    Path:     /Users/dude/.docker/cli-plugins/docker-scout

Server:
 Containers: 0
  Running: 0
  Paused: 0
  Stopped: 0
 Images: 2
 Server Version: 27.3.1
 Storage Driver: overlayfs
  driver-type: io.containerd.snapshotter.v1
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 472731909fa34bd7bc9c087e4c27943f9835f111
 runc version: v1.1.13-0-g58aa920
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
  cgroupns
 Kernel Version: 6.10.14-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: aarch64
 CPUs: 12
 Total Memory: 7.653GiB
 Name: docker-desktop
 ID: c8d6af47-14f4-47e2-a908-fcf7a18309f4
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 No Proxy: hubproxy.docker.internal
 Labels:
  com.docker.desktop.address=unix:///Users/dude/Library/Containers/com.docker.docker/Data/docker-cli.sock
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5555
  127.0.0.0/8
 Live Restore Enabled: false

[Tpuljak]

root               988   0.0  0.2 412264112  87776   ??  Ss   Tue06PM  20:06.80 /usr/local/bin/daytona daemon-serve

@dhirjgupta as you can see here, the server is indeed started with the root user.

I suggest the following:

sudo daytona server stop
sudo daytona purge # This will remove daytona config files from your system
curl -sf -L https://download.daytona.io/daytona/install.sh | sudo bash # To reinstall daytona
daytona server -y
daytona create

[dhirjgupta]

Thanks @Tpuljak - I will test this out tonight / this weekend and post here with an update.

[dhirjgupta]

Hi @Tpuljak I tried the steps recommended and got:

Dhirjs-MacBook-Pro:~ dude$ daytona server -y

 Starting the Daytona Server daemon...

FATA[0000] open /Users/dude/Library/Application Support/daytona/server/daytona.log: permission denied

I tried changing the ownership of that daytona directory and got

daytona server -y

 Starting the Daytona Server daemon...

FATA[0000] "launchctl" failed with stderr: Load failed: 5: Input/output error
Try running `launchctl bootstrap` as root for richer errors.

and same with stop

Dhirjs-MacBook-Pro:Application Support dude$ sudo daytona server stop

 Stopping the Daytona Server daemon...

FATA[0000] "launchctl" failed with stderr: Unload failed: 5: Input/output error
Try running `launchctl bootout` as root for richer errors.

[Tpuljak]

@dhirjgupta you shouldn't run these commands with sudo. It's important to always run them under the same user.

Let's try this.

launchctl unload ~/Library/LaunchAgents/DaytonaServerDaemon.plist
sudo rm -rf ~/Library/Application\ Support/daytona
curl -sf -L https://download.daytona.io/daytona/install.sh | sudo bash
daytona server -y