make stop error

[geoffgeoffgeoff3]

I pulled all the new changes, and did make start. I tried to access http://localhost:7827/starexec but get ...

I think it might be because I'm in California and using the VPN. I'll test again when I get back to Miami.

So I did make stop and there's an error that might need attention ...

> make stop
Removing Podman deployment (volumes preserved)
Cleaning up existing StarExec pods, containers, and secrets...
  Initiating graceful shutdown (10s timeout) for pods with label app.kubernetes.io/instance=starexec...
ERRO[0000] Unable to clean up network for container b52ce98febfcd4469bc212cd7f28261b2bdf9e10a38cd37002027c48450a0979: "unmounting network namespace for container b52ce98febfcd4469bc212cd7f28261b2bdf9e10a38cd37002027c48450a0979: failed to remove ns path /run/user/10248/netns/netns-fdd70938-4cb8-c6fd-f894-1b5ef21e3c05: remove /run/user/10248/netns/netns-fdd70938-4cb8-c6fd-f894-1b5ef21e3c05: device or resource busy"
d42be4702a94f2962ca7c065e6ff8c788dd3c5bae4ecad944ef62646161e4710
  Attempting forceful removal of pod d42be4702a94...
d42be4702a94f2962ca7c065e6ff8c788dd3c5bae4ecad944ef62646161e4710
  ✓ Pod d42be4702a94 removed cleanly.
  Removing secrets matching name starexec
f76bc70c1973a120c6e4f7349
Waiting for resources to be fully released...

✓ Cleanup complete (volumes preserved)

[AndresCdo]

Pretty sure this is on you set up, and the warning is just noise from podman. The logic I did introduce is robust.