-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Do not leak libpod package into the remote client #9716
Do not leak libpod package into the remote client #9716
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Luap99 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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.
LGTM
The `libpod/network` package should only be used on the backend and not the client. The client used this package only for two functions so move them into a new `pkg/network` package. This is needed so we can put linux only code into `libpod/network`, see containers#9710. [NO TESTS NEEDED] Signed-off-by: Paul Holzinger <[email protected]>
Some packages used by the remote client imported the libpod package. This is not wanted because it adds unnecessary bloat to the client and also causes problems with platform specific code(linux only), see containers#9710. The solution is to move the used functions/variables into extra packages which do not import libpod. This change shrinks the remote client size more than 6MB compared to the current master. [NO TESTS NEEDED] I have no idea how to test this properly but with containers#9710 the cross compile should fail. Signed-off-by: Paul Holzinger <[email protected]>
Damn fine work, LGTM
…On Mon, Mar 15, 2021 at 08:54 Valentin Rothberg ***@***.***> wrote:
***@***.**** commented on this pull request.
LGTM
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#9716 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB3AOCDPOG7DUFXAUHXPC23TDX7RFANCNFSM4ZGPWGFQ>
.
|
The New York timezone changes between summer and winter time. Make sure the test allows both timezones. Signed-off-by: Paul Holzinger <[email protected]>
Tests are green. Merge me |
/lgtm |
The
libpod/network
package should only be used on the backend and not theclient. The client used this package only for two functions so move them
into a new
pkg/network
package.Some packages used by the remote client imported the libpod package.
This is not wanted because it adds unnecessary bloat to the client and
also causes problems with platform specific code(linux only), see Network prune filters for http api (compat and libpod) #9710.
The solution is to move the used functions/variables into extra packages
which do not import libpod.
This change shrinks the remote client size more than 6MB compared to the
current master.
[NO TESTS NEEDED]
I have no idea how to test this properly but with #9710 the cross
compile should fail.