balena-supervisor/test/data/docker-states/network-mode-service/compose.json

{
	"imageId": 431889,
	"serviceName": "main",
	"image": "sha256:f9e0fa6e3e68caedbcbb4ef35d5a8dce2a8d33e39cc94115d567800f25d826f4",
	"running": true,
	"appId": 1011165,
	"releaseId": 572579,
	"serviceId": 43697,
	"commit": "b14730d691467ab0f448a308af6bf839",
	"imageName": "registry2.resin.io/v2/8ddbe4a22e881f06def0f31400bfb6de@sha256:09b0db9e71cead5f91107fc9254b1af7088444cc6da55afa2da595940f72a34a",
	"tty": true,
	"network_mode": "service: test"
}
Support network_modes of service:<servicename> That way that this is performed is by first adding a depends_on entry for the target service if it appears in a network mode. Then when we generate the docker container for this service, we use the containerId of the target container and replace the network_mode with `container:<id>`. When comparing state, we check that the containerId still points to the contianerId of the target container, and in this way we ensure that when a network mode target container changes, we change the dependent container too. Change-type: minor Closes: #851 Signed-off-by: Cameron Diver <cameron@balena.io> 2019-07-12 16:36:40 +01:00			`{`
			`"imageId": 431889,`
			`"serviceName": "main",`
			`"image": "sha256:f9e0fa6e3e68caedbcbb4ef35d5a8dce2a8d33e39cc94115d567800f25d826f4",`
			`"running": true,`
			`"appId": 1011165,`
			`"releaseId": 572579,`
			`"serviceId": 43697,`
			`"commit": "b14730d691467ab0f448a308af6bf839",`
			`"imageName": "registry2.resin.io/v2/8ddbe4a22e881f06def0f31400bfb6de@sha256:09b0db9e71cead5f91107fc9254b1af7088444cc6da55afa2da595940f72a34a",`
			`"tty": true,`
			`"network_mode": "service: test"`
			`}`