Skip to content

Embedded launch script fails if jar is owned by an unknown user #29370

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.

Sign up for GitHub

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

Jump to bottom
Closed
philwebb opened this issue Jan 12, 2022 · 0 comments
Closed

Embedded launch script fails if jar is owned by an unknown user #29370

philwebb opened this issue Jan 12, 2022 · 0 comments
Assignees
@philwebb
Labels
type: bug A general bug
Milestone
2.5.9

Comments

@philwebb
Copy link
Member

Currently our launch script runs applications as the owner of the jar file. In some situations it's possible that the jar file might be set with an owner that doesn't exist.

This problem happens with our own build in SysVinitLaunchScriptIntegrationTests. When running locally, the test jar file can be owned by a user that doesn't exist in the Docker container.
@philwebb philwebb added the type: bug A general bug label Jan 12, 2022
@philwebb philwebb added this to the 2.5.9 milestone Jan 12, 2022
@philwebb philwebb self-assigned this Jan 12, 2022
@philwebb philwebb mentioned this issue Jan 12, 2022
Closed
philwebb added a commit that referenced this issue Jan 12, 2022
@philwebb
Log Docker output to aid debugging
7c16668 
Add an SLF4J logger so that we can see real time output of the
Docker container.

See gh-29370
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@philwebb philwebb

Labels
type: bug A general bug
Projects
None yet
Milestone
2.5.9
Development

No branches or pull requests
1 participant
@philwebb