abiosoft / abiosoft/colima

Wrong uid/gid on mount point

Ouverte
#1,406 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub
Langage dominant
Go
Étoiles
30.8k
Forks
613
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

### Description

Hello, I've just opened a bug on Lima: https://github.com/lima-vm/lima/issues/4053

You can find all the information there, just tried Colima just to exclude other causes but I confirm that even on Colima the bug is present.

Basically the issue is this, for those who don't want to read through the full Lima issue, here's a quick recap: I'm seeing inconsistent directory ownership mapping when using VirtioFS between my macOS host and Lima VM. Files show correct ownership, but directories show different ownership depending on the context from which you view them.

```bash
# View directory contents from inside the mounted directory
❯ docker run -u 501 --rm -v $PWD:/test alpine:latest ash -c "ls -al /test"
drwxr-xr-x 6 501 root 192 Sep 19 07:59 .
drwxr-xr-x 1 root root 4096 Sep 19 08:04 ..
drwxr-xr-x 9 501 root 288 Sep 19 07:58 .git
-rw-r--r-- 1 501 root 47 Sep 19 07:59 Dockerfile
-rw-r--r-- 1 501 root 0 Sep 19 06:58 file
drwxr-xr-x 3 501 root 96 Sep 19 08:00 subdir

# View the same directory from root level
❯ docker run -u 501 --rm -v $PWD:/test alpine:latest ash -c "ls -al / | grep test"
drwxr-xr-x 3 root root 96 Sep 19 06:58 test
```

What I'm seeing:
1. **Inside the directory**: `drwxr-xr-x 3 501 root` - correct, shows I own it ✅
2. **From root level**: `drwxr-xr-x 3 root root` - incorrect, shows root owns it ❌
3. **Files**: `501:root` - correct ✅

The same behaviour is present on Colima.

Have you ever noticed or been impacted by this? We're trying to migrate away from Docker Desktop, but several tools are failing because of it.

### Version

_No response_

### Operating System

- [ ] macOS Intel <= 13 (Ventura)
- [ ] macOS Intel >= 14 (Sonoma)
- [ ] Apple Silicon <= 13 (Ventura)
- [ ] Apple Silicon >= 14 (Sonoma)
- [ ] Linux

### Output of `colima status`

_No response_

### Reproduction Steps

1.
2.
3.

### Expected behaviour

_No response_

### Additional context

_No response_

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.