Previously we had no docker start or docker stop support in the Docker ACI integration. This was because ACI does not support a stop or start commands in the same way that Moby does.
We have now added these commands accepting the difference to get feedback on whether this is an acceptable approach.
From a user perspective the main difference with ACI is that when your container that has been previously stopped is started again it will have not retained the state within the container. You will still retain your IP address as this is maintained by the container group and you can still inspect the logs of the stopped container.
If you find this difference acceptable or have a use case where this does not work please let us know on this issue.
Previously we had no
docker startordocker stopsupport in the Docker ACI integration. This was because ACI does not support a stop or start commands in the same way that Moby does.We have now added these commands accepting the difference to get feedback on whether this is an acceptable approach.
From a user perspective the main difference with ACI is that when your container that has been previously stopped is started again it will have not retained the state within the container. You will still retain your IP address as this is maintained by the container group and you can still inspect the logs of the stopped container.
If you find this difference acceptable or have a use case where this does not work please let us know on this issue.
As a note generally container state is best stored in a volume, to find out more about Docker volumes see https://docs.docker.com/storage/volumes/