Skip to content

not passed cap-add docker option. #60

@sergey-safarov

Description

@sergey-safarov

I have defined actions like

    - uses: addnab/docker-run-action@v3
      with:
        image: ${{some-image}}
        options: -v ${{ github.workspace }}:/usr/src/my-sources --cap-add chown 
        run: |
          cd /usr/src/my-sources
          chown -R user:group *

Where ${{some-image}} executes the commands under user permissions. When docker process container starts with --cap-add chown, then this works without any issues. But this script generates errors like

chown: some_file: Operation not permitted

I have checked docker command in the actions logs and see volume mount passed properly, but --cap-add chown options are stripped.
Could you add the ability to pass --cap-add options?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions