Skip to content
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.

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

Homepage vols #407

Merged
merged 15 commits into from
Apr 1, 2025
Merged

Homepage vols #407

merged 15 commits into from
Apr 1, 2025

Conversation

mcmikemn
Copy link
Collaborator

@mcmikemn mcmikemn commented Apr 1, 2025

Change volume mount to :ro, apparently required for homepage to use docker sockets as mounted volumes (which is a good thing) - I think this is new to a Homepage upgrade.

@mcmikemn mcmikemn added the bug Something isn't working label Apr 1, 2025
@mcmikemn mcmikemn self-assigned this Apr 1, 2025
@mcmikemn mcmikemn closed this Apr 1, 2025
@mcmikemn mcmikemn reopened this Apr 1, 2025
@mcmikemn
Copy link
Collaborator Author

mcmikemn commented Apr 1, 2025

Also, apparently, I made this branch from my "bumps" branch so that I'd be using the current Homepage version. Oh well, now is as good a time as any to also push these bumps.

@mcmikemn mcmikemn requested a review from EnigmaCurry April 1, 2025 09:39
@EnigmaCurry
Copy link
Owner

There is no way to prevent write access to a mounted socket. The :ro is security theater. It still allows full write access to docker. The only benefit it has is to prevent unlinking the socket from inside the container (but not sure why a container would do that).

The only true way to limit access to docker is through a docker-proxy.

@EnigmaCurry
Copy link
Owner

EnigmaCurry commented Apr 1, 2025

I'll allow you to keep the :ro, even though it changes little. I just wanted you to know that it doesnt do what it appears to do.

…in docker-compose.yaml. Update .env-dist comments.
@mcmikemn
Copy link
Collaborator Author

mcmikemn commented Apr 1, 2025

I removed the :ro. My tests showed that I needed it, but I think I was conflating 3 different issues that I was testing at the same time. We don't want to support mounting docker sockets, which is why we left HOMEPAGE_EXTRA_VOLUMES in .env-dist but didn't add it to Makefile. And it's possible that someone might want to mount a volume with write access.

@mcmikemn mcmikemn requested a review from EnigmaCurry April 1, 2025 14:59
@EnigmaCurry
Copy link
Owner

LGTM

@mcmikemn mcmikemn dismissed EnigmaCurry’s stale review April 1, 2025 15:43

Fixed, discussed with EnigmaCurry.

@mcmikemn
Copy link
Collaborator Author

mcmikemn commented Apr 1, 2025

LGTM

There was still a fix request from you even though I marked it "resolved" in the conversation. I couldn't resolve the request so I dismissed it. But I still can't merge the PR, so I guess you have to approve or dismiss the fix request, or just approve the PR.

@EnigmaCurry
Copy link
Owner

I think it is just waiting for you to request another review

@mcmikemn mcmikemn requested a review from EnigmaCurry April 1, 2025 15:47
@EnigmaCurry EnigmaCurry merged commit 4da2c04 into master Apr 1, 2025
@EnigmaCurry EnigmaCurry deleted the homepage-vols branch April 1, 2025 15:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants