Docker Container Runs Repeatedly After Successful Check In

[jdholtz]

Docker Container Runs Repeatedly After Successful Check In

[jdholtz]

I can get this information. However, I think it would be helpful to still notify people if it has already been checked in. Maybe a You have already checked in message?

[grantland]

The main issue is that it continues to check in after successfully checking in the first time as I would expect the instance to exit with a successful response after the first successful check in.

[jdholtz]

Are these messages happening in the same instance of the script (i.e. it didn’t restart)? It should exit right after it has checked in. How much time passes in between attempts?

[grantland]

Same instance of the script and pretty much a few seconds in between

[jdholtz]

This might be an issue running it with Docker and the restart policy you are giving the container. Are you using ––restart-policy=always? I think the container exits and restarts which explains why it keeps checking in (Docker doesn’t clear logs on a restart).

If you want Docker to start on boot, I think you can still use the unless-stopped or on-failure restart policy without having this side effect. Let me know if this is the issue and I will update the README accordingly.

[grantland]

I used the following command:

docker run -d --restart unless-stopped auto-southwest-check-in CONFIRMATION FIRST LAST

[jdholtz]

Could you try it with the on-failed restart policy and see if it has the same issue? And if that doesn’t work, can you try it without Docker to see if it is Docker or the script (No worries if you can’t)?

[grantland]

You're right! I was using the wrong --restart flag and --restart on-failure solves the problem. Thanks!

[jdholtz]

Great! I’ll add that to the README to prevent others from having this issue. Thanks for bringing it up

[jdholtz]

Edited the title for clarity