-
Notifications
You must be signed in to change notification settings - Fork 56
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
fix(*) only mount logs directory and use a different prefix #474
Conversation
where are the unix sockets currently located? At the top of the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Am I correct we loose access to everything but the logs? eg. no way to inspect the generated nginx config files from the host?
yes
yes, others are not being re-mounted or symlinked in this PR. As from the comments that logs are the reason we use prefix from mount at first place, so that is being implemented here as first iterration. |
7865ccf
to
1cbf26c
Compare
08cd14d
to
29b91ef
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
somehow I still see the files appear on the mount.
That's because I used the old containers. |
1e522d4
to
2b7e889
Compare
services: | ||
kong: | ||
volumes: | ||
- ${PONGO_WD}/servroot:/kong-prefix |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@fffonion mind having a look? I think we can remove the one from the main docker compose file no?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
actually no conflict here, the mount from main file is for getting in the plugin code for test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pwd -> /kong-plugin
pwd/servroot -> /kong-prefix
we can't do
pwd/servroot -> /kong-plugin/servroot
anymore because that will be a bind mount on host and not supported on macos
2b7e889
to
89d163b
Compare
@fffonion can you squash the commits first, and then merge (squashing via ui is disabled) |
nvm I'll do it |
Thank you @Tieske |
(cherry picked from commit 8660faf)
Pongo mounts
/kong-plugin
to current folder and use/kong-plugin/servroot
as default prefixso that developer can easily access logs. On macOS, such directory is implemented as VM file shared
and doesn't support binding a unix domain socket; on windows, if current directory from the 9p fs shared
from Windows volumes, binding unix domain socket is also not supported.
This fix makes only
$KONG_PREFIX/logs
a mount from host on such platform, thus makes Kong able to start.This is considered a short term fix until Kong implemented to move UDS sockets to a subdirectory. By then,
the whole $KONG_PREFIX can be mounted again, while the sockets subdirectory will become a symlink.
KAG-5588
KAG-3284