OpenLiberty / OpenLiberty/ci.docker

For UBI images is chmod -R u+x /usr/bin necessary?

Open
#382 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
48
Forks
60
Avg merge
3h 2m
Merged PRs (30d)
3

Description

See https://github.com/OpenLiberty/ci.docker/blob/ef3acaf285957111a2d7da60eb1bd2cb363ed7ca/releases/latest/full/Dockerfile.ubi.openjdk17#L29

It would be good if we could avoid doing this. If this changes any attributes on the files it is like copying a whole new file into our liberty layer of the image.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at line 29 of releases/latest/full/Dockerfile.ubi.openjdk17 and inspect the chmod command in the surrounding image-layer setup. Determine whether it is required for the UBI image, then verify that removing it preserves expected executable behavior and avoids unnecessary file-attribute changes.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, shell
Domain
build-system, devops
Issue type
Refactor
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.