Paul Holzinger 57e8c66322 Do not leak libpod package into the remote client ... 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 #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. Signed-off-by: Paul Holzinger <paul.holzinger@web.de>		2021-03-15 14:02:04 +01:00
..
completion.go	Do not leak libpod package into the remote client	2021-03-15 14:02:04 +01:00
create.go	bump go module to v3	2021-02-22 09:03:51 +01:00
create_opts.go	Compat API: Avoid trying to create volumes if they already exist	2021-03-08 15:18:42 -03:00
createparse.go	bump go module to v3	2021-02-22 09:03:51 +01:00
default.go	bump go module to v3	2021-02-22 09:03:51 +01:00
diffChanges.go	bump go module to v3	2021-02-22 09:03:51 +01:00
netflags.go	Enable no_hosts from containers.conf	2021-02-26 06:37:48 -05:00
ports.go	V2 enable ps tests	2020-04-29 15:51:37 -07:00
specgen.go	Do not leak libpod package into the remote client	2021-03-15 14:02:04 +01:00
util.go	bump go module to v3	2021-02-22 09:03:51 +01:00
volumes.go	replace local mount consts with libpod/define	2021-03-07 12:03:34 +01:00