Skip to content

Conversation

@anthony-chu
Copy link
Member

@anthony-chu anthony-chu force-pushed the LPD-69550 branch 3 times, most recently from 192fcbb to 83cf7d5 Compare October 22, 2025 17:51
Copy link
Member

@drewbrokke drewbrokke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@anthony-chu how does this behave if Glowroot is not enabled? Any side-effects?

@drewbrokke
Copy link
Member

@anthony-chu sorry just merged Anna's PR, there's a merge conflict now.

@anthony-chu anthony-chu marked this pull request as draft October 24, 2025 16:43
@anthony-chu
Copy link
Member Author

This will probably need to wait for the new volume export/import changes to go in first, since this PR modifies the (soon-to-be) mostly defunct helper Dockerfile.


COPY --chown=1000:1000 ${DATA_DIRECTORY} /container-data

RUN mkdir -p /container-data/glowroot && chown -R 1000:1000 /container-data/glowroot
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this line needed for glowroot but not any other services? Why wouldn't you need to do this for the liferay service as well?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the liferay volume didn't need this because it points to a directory that already exists in the liferay/dxp image (/opt/liferay/data); docker copies the existing content into the volume. on the other hand, the glowroot volume points to a directory that doesn't exist in the volume (/opt/liferay/glowroot/data, the important part being the .../data directory); since the data directory doesn't already exist in /opt/liferay/glowroot directory (which does exist), then docker creates it, and it gets created with root permissions.

i checked with Jordi, and he mentioned that they did not need anything else from the /opt/liferay/glowroot directory besides the data folder; however, we would need to do the above if the glowroot volume were tied only to the /opt/liferay/glowroot/data directory. if, instead, it pointed to the /opt/liferay/glowroot directory more broadly, then we wouldn't need to chown.

if that's sufficient enough of a workaround for our case (i've already tested that it works), then i can switch the glowroot volume just to point to /opt/liferay/glowroot and get rid of the chown.

@drewbrokke
Copy link
Member

@anthony-chu I think you can start re-working this one on top of #165.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants