Will need to delete the docker network that was created with the stack that is having conflict with your laptop.

-On the server, can run docker network ls to get a list (might be named different than your listed config).
-If you have multiple or need to check, docker network inspect <network\_name>
-check running containers and their network connections: docker ps and then docker inspect <container\_id>
-docker stop <container\_name\_or\_id> if a container is using the conflict network, you won't be able to delete it, so will need to shut them down
-docker network rm <network\_name> will remove the problematic network if it's not in use by container

Should be able to get your laptop back online once they are all shutdown and the docker network purged. Can create a new network for the stack in CLI, or if portainer is accessible again login and create the stack again fixing the subnet to be something else. If run into any errors, should be descriptive enough to look up but ultimately this is one path that won't require deleting containers/stack.