prevent abra app cp from applying file permissions. #525

Closed
opened 2023-10-24 16:57:42 +00:00 by moritz · 2 comments
Member

When I run abra app cp to copy files from a container to my local system I get the following error:
FATA[0008] failed to Lchown "filename.tar.gz" for UID 0, GID 0: lchown filename.tar.gz: operation not permitted.
The reason is that abra tries to change the owner of the file on my local system to the same owner as of the container, which is root.
In the end everything works fine and the file is copied. But abra returns a non zero return code, which causes problems if I want to run abra from other scripts and check if it was successfully.

When I run `abra app cp` to copy files from a container to my local system I get the following error: `FATA[0008] failed to Lchown "filename.tar.gz" for UID 0, GID 0: lchown filename.tar.gz: operation not permitted`. The reason is that abra tries to change the owner of the file on my local system to the same owner as of the container, which is `root`. In the end everything works fine and the file is copied. But abra returns a non zero return code, which causes problems if I want to run abra from other scripts and check if it was successfully.
moritz added the
bug
label 2023-10-24 16:57:42 +00:00
decentral1se added the
abra
label 2023-10-28 12:14:00 +00:00
Member

I think this got fixed in coop-cloud/abra#390. It now always sets the file ownership to the local user.
Maybe now we need a flag to use the original permissions?

I think this got fixed in https://git.coopcloud.tech/coop-cloud/abra/pulls/390. It now always sets the file ownership to the local user. Maybe now we need a flag to use the original permissions?
Author
Member

I think this got fixed in coop-cloud/abra#390. It now always sets the file ownership to the local user.
Maybe now we need a flag to use the original permissions?

I think its a good idea, I opened a followup issue: #542

> I think this got fixed in https://git.coopcloud.tech/coop-cloud/abra/pulls/390. It now always sets the file ownership to the local user. > Maybe now we need a flag to use the original permissions? I think its a good idea, I opened a followup issue: https://git.coopcloud.tech/coop-cloud/organising/issues/542
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/organising#525
No description provided.