# Stopping the k3s service does not stop the containers

**URL:** <https://forum.ansible.com/t/stopping-the-k3s-service-does-not-stop-the-containers/37722>\
**Category:** AWX Project\
**Created:** [March 3, 2023, 1:16pm UTC](https://forum.ansible.com/t/stopping-the-k3s-service-does-not-stop-the-containers/37722 "2023-03-03T13:16:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mjksohonet](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mjksohonet/32/1217_2.png) [@mjksohonet](https://forum.ansible.com/u/mjksohonet)\
**Post date:** [March 3, 2023, 1:16pm UTC](https://forum.ansible.com/t/stopping-the-k3s-service-does-not-stop-the-containers/37722/1 "2023-03-03T13:16:17Z")

</div>

Is this the expected/desired outcome?

---

<div class="post-metadata">

**Author:** ![AWX\_Project](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@AWX\_Project](https://forum.ansible.com/u/AWX_Project)\
**Post date:** [March 3, 2023, 6:34pm UTC](https://forum.ansible.com/t/stopping-the-k3s-service-does-not-stop-the-containers/37722/2 "2023-03-03T18:34:18Z")

</div>

what commands are you running to stop the k3s service?

AWX Team

---

<div class="post-metadata">

**Author:** ![mjksohonet](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mjksohonet/32/1217_2.png) [@mjksohonet](https://forum.ansible.com/u/mjksohonet)\
**Post date:** [March 6, 2023, 5:19pm UTC](https://forum.ansible.com/t/stopping-the-k3s-service-does-not-stop-the-containers/37722/3 "2023-03-06T17:19:08Z")

</div>

_systemctl stop k3s.service_

might it be caused by the lack of an ExecStop command that, presumably, would run the /usr/local/bin/k3s-killall-sh script?