Felipe Lalanne 416170bc05 Ignore expose service compose configuration ... The docker EXPOSE directive and corresponding docker-compose `expose` service configuration serves as documentation/metadata that a container listens on a certain port that may be used for service discovery but it doesn't have any real impact on the ability for other containers on the same network to access the exposed service via the port. In newer engine implementations, this property may conflict with other network configurations, and prevent the container from being started by the docker engine (see #2211). This PR removes code that would manage the expose property and takes the property out of the whitelist. A composition with the `expose` property will result in the log message `Ignoring unsupported or unknown compose fields: expose`. While this change should not have operational impact, it still removes a previously supported configuration and as such there is a chance of it being a breaking change for some applications. For this reason it is being published as a new major version. Change-type: major Closes: #2211		2023-10-23 11:41:32 -03:00
..
app.spec.ts	Improve tests surrounding Engine-host race patch	2023-06-19 11:11:26 -07:00
network.spec.ts	Create default network as config-only when services have host networking	2022-11-16 10:19:36 -08:00
ports.spec.ts	Ignore expose service compose configuration	2023-10-23 11:41:32 -03:00
service.spec.ts	Ignore expose service compose configuration	2023-10-23 11:41:32 -03:00
utils.spec.ts	Parse container exit error message instead of status	2023-06-22 14:43:17 -07:00
volume.spec.ts	Split compose/volume tests into unit/integration	2022-09-28 10:37:40 -03:00