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
Permission Denied Error #171
Comments
Does your user have write permission for the directory you are running in? |
@andydotxyz Yes,
|
@andydotxyz the error is from inside the container. Which directory does it map to in the host sytem? |
The current directory, by default. Maybe your disk ran out of space? Or Docker is running as a user who cannot write to your files? The clearing of old builds message isn't proof it can write, as if they were missing it wouldn't have to do anything. |
@andydotxyz @Jacalz My current user has all the permissions. And I'm able to run helloworld docker. But with fyne it throws this error. ▶ id
uid=1003(abhisek) gid=998(docker) groups=998(docker),27(sudo),139(libvirt),1003(abhisek) My disk has a lot of space too ▶ df -h /
Filesystem Size Used Avail Use% Mounted on
/dev/sda9 122G 110G 6.8G 95% / |
Can you please help me settings these things manually? I will create a custom docker and would like fyne-cross use that instead? |
I think it is not a docker image problem, but that docker doesn't have access to your app subdirectory. You can try the following command to check:
|
@Bluebugs That's throwing an error
|
@Bluebugs This is the full output
|
@Bluebugs But this command works fine without the
A file is created properly. |
My docker version ▶ docker -v
Docker version 20.10.22, build 3a2c30b |
That's interesting. @lucor, I think you have a better knowledge here than I do, any guess what could be going on? |
running in a project idx workspace. rootless docker. I had to do the following at various stages
This still results in
While last step failed, I still got the output zip file. This seems like docker shenanigans. fyne-cross's docker images are not properly doing the sub-uid/gid stuff. Maybe you guys are using rootful docker so doesn't get affected by these. I use podman (which is by default rootless) in my own pc, so can't provide more insight. But It has been my experience that people assume rootful docker when building container images and those images craps out when it doesn't have that whole rootful docker permissions. |
We are definitely not supporting rootless docker. Only podman rootless is supported. Is that the case here, we are talking about rootless docker? |
It could be that because your user isn't 1000 you are getting issues. I've had issues with docker container permissions before where containers only work if your uid is 1000. |
Describe the bug:
To Reproduce:
Steps to reproduce the behaviour:
Device and debug info (please complete the following information):
Debug info
The text was updated successfully, but these errors were encountered: