# Best practice of stopping InfluxDB inside a docker container without stopping the container

**URL:** <https://community.influxdata.com/t/best-practice-of-stopping-influxdb-inside-a-docker-container-without-stopping-the-container/28455>\
**Category:** InfluxDB 2\
**Tags:** cli\
**Created:** [February 6, 2023, 2:38pm UTC](https://community.influxdata.com/t/best-practice-of-stopping-influxdb-inside-a-docker-container-without-stopping-the-container/28455 "2023-02-06T14:38:35Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Jeffrey](https://sea1.discourse-cdn.com/flex023/user_avatar/community.influxdata.com/jeffrey/32/10944_2.png) [@Jeffrey](https://community.influxdata.com/u/Jeffrey)\
**Post date:** [February 8, 2023, 1:13pm UTC](https://community.influxdata.com/t/best-practice-of-stopping-influxdb-inside-a-docker-container-without-stopping-the-container/28455/4 "2023-02-08T13:13:24Z")

</div>

For the first part, my guess would be something is wrong with the pathing of your volume and the bolt file is not actually there. Looks like you have `/var/lib/influxdb/influxd.bolt` and you might want `/var/lib/influxdb2/influxd.bolt`? You can also verify on your local machine if that bucket actually exists by using the [boltdbweb tool](https://github.com/evnix/boltdbweb) to inspect the file. If that bucket is not there, something has gone wrong writing the file, and if it is there then it may be a recovery bug.

The Release notes have a bit of an explanation and a link out to the rest of the docs that may help explain the login capability [influx CLI release notes | InfluxDB OSS 2.6 Documentation](https://docs.influxdata.com/influxdb/v2.6/reference/release-notes/influx-cli/#features)

---

_[View the full topic](https://community.influxdata.com/t/best-practice-of-stopping-influxdb-inside-a-docker-container-without-stopping-the-container/28455)._