Thanks Anthony The volume bind command looks like this -v /tmp/ceph-tmp-wvh4u18:/tmp/monmap:z so i guess the /tmp/ceph-tmp-xxxx never gets created so there is nothing to map What would be the solution though ...I tried removing and reinstalling docker Update and upgrade ( Ubuntu 24.04.2 LTS) On Thu, 24 Jul 2025 at 11:09, Anthony D'Atri <anthony.datri@gmail.com> wrote:
How did you get that attachment through the list? Curious.
I think /tmp/monmap is relative to the directory tree that the container sees:
-v /tmp/ceph-tmp-wvh4u18:/tmp/monmapz
Because of the wrapping I’m not sure about the z on the next line, but -v can be considered like a bind mount of the first path so that container sees it on the second path.
Now, as to what happened to /tmp/ceph-tmpxxxx, I can’t say.
On Jul 24, 2025, at 10:53 AM, Steven Vacaroaia <stef97@gmail.com> wrote:
Hi,
I had to zap and start from scratch my cluster and now I cannot bootstrap using cephadm
The error is " monmaptool: error writing to /tmp/monmap: (21) Is a directory "
There is no /tmp/monmap directory though
I also made sure there is nothing in /var/lib/ceph, no "ceph" process , nothing in /etc/systemd/system/ceph* or /etc/ceph AND rebooted the server
Any help will be appreciated
Many thanks Steven
<image.png> _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io