After installing Gladys on a USB key, it works fine.
But:
We realized that the docker daemon had not started, why?
This probably means that the zigbee2mqtt integration does not work.
I followed the same procedure as for an SD card.
Is there an additional command to run? That’s weird.
What is the command to start the docker daemon?
Can you tell us more about how you installed Gladys precisely?
I flashed the image of Gladys with Etcher.
It’s not the latest one available on the site, but it was version 4.1 or 4.2 as far as I remember.
I also followed a tutorial to make my Pi 3b+ boot from USB.
Can you provide more details about the tutorial you followed? ^^ Without information, it’s impossible to help you 
As always:
I was talking about that one
I thought so too!
The Raspberry Pi Foundation’s flasher natively supports flashing to USB keys or SSDs, if I’m not mistaken
Okay
What does that mean?
No more tinkering, it’s native
https://www.raspberrypi.org/software/
But I don’t think that’s the source of your problem.
Update your pi:
sudo apt update && sudo apt upgrade -y
And reboot
sudo reboot
Then check with docker logs if it’s good
pi@gladys:~ $ sudo apt update && sudo apt upgrade -y
0% [Working]
Ign:1 http://raspbian.raspberrypi.org/raspbian buster InRelease
0% [Connecting to download.docker.com] [Waiting for headers]
Ign:2 http://archive.raspberrypi.org/debian buster InRelease
0% [Connecting to raspbian.raspberrypi.org (93.93.128.193)] [Connecting to down
Err:3 http://archive.raspberrypi.org/debian buster Release
Could not open file /var/lib/apt/lists/partial/archive.raspberrypi.org_debian_dists_buster_Release - open (30: Read-only file system) [IP: 2a00:1098:84:1e0::3 80]
0% [Waiting for headers] [Connected to download.docker.com (2600:9000:21d7:d000
Err:4 http://raspbian.raspberrypi.org/raspbian buster Release
Could not open file /var/lib/apt/lists/partial/raspbian.raspberrypi.org_raspbian_dists_buster_Release - open (30: Read-only file system) [IP: 93.93.128.193 80]
0% [Connected to download.docker.com (2600:9000:21d7:d000:3:db06:4200:93a1)]
Hit:5 https://download.docker.com/linux/raspbian buster InRelease
0% [Working]
Err:5 https://download.docker.com/linux/raspbian buster InRelease
Couldn't create temporary file /tmp/apt.conf.cIETDd for passing config to apt-key
0% [Working]
Reading package lists... 0%
Reading package lists... 100%
Reading package lists... Done
W: chown to _apt:root of directory /var/lib/apt/lists/partial failed - SetupAPTPartialDirectory (30: Read-only file system)
W: chmod 0700 of directory /var/lib/apt/lists/partial failed - SetupAPTPartialDirectory (30: Read-only file system)
W: chown to _apt:root of directory /var/lib/apt/lists/auxfiles failed - SetupAPTPartialDirectory (30: Read-only file system)
W: chmod 0700 of directory /var/lib/apt/lists/auxfiles failed - SetupAPTPartialDirectory (30: Read-only file system)
W: Not using locking for read only lock file /var/lib/apt/lists/lock
W: Problem unlinking the file /var/lib/apt/lists/partial/.apt-acquire-privs-test.nxvcTc - IsAccessibleBySandboxUser (30: Read-only file system)
W: Problem unlinking the file /var/lib/apt/lists/partial/.apt-acquire-privs-test.46tpDu - IsAccessibleBySandboxUser (30: Read-only file system)
W: Problem unlinking the file /var/lib/apt/lists/partial/.apt-acquire-privs-test.vKGanM - IsAccessibleBySandboxUser (30: Read-only file system)
W: Problem unlinking the file /var/lib/apt/lists/partial/raspbian.raspberrypi.org_raspbian_dists_buster_InRelease - PrepareFiles (30: Read-only file system)
W: Problem unlinking the file /var/lib/apt/lists/partial/archive.raspberrypi.org_debian_dists_buster_InRelease - PrepareFiles (30: Read-only file system)
W: Problem unlinking the file /var/lib/apt/lists/partial/archive.raspberrypi.org_debian_dists_buster_Release - PrepareFiles (30: Read-only file system)
E: The repository 'http://archive.raspberrypi.org/debian buster Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: Problem unlinking the file /var/lib/apt/lists/partial/raspbian.raspberrypi.org_raspbian_dists_buster_Release - PrepareFiles (30: Read-only file system)
E: The repository 'http://raspbian.raspberrypi.org/raspbian buster Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: Problem unlinking the file /var/lib/apt/lists/partial/download.docker.com_linux_raspbian_dists_buster_InRelease - PrepareFiles (30: Read-only file system)
W: chown to _apt:root of file /var/lib/apt/lists/download.docker.com_linux_raspbian_dists_buster_InRelease failed - Item::QueueURI (30: Read-only file system)
W: chmod 0600 of file /var/lib/apt/lists/download.docker.com_linux_raspbian_dists_buster_InRelease failed - Item::QueueURI (30: Read-only file system)
W: chown to root:root of file /var/lib/apt/lists/download.docker.com_linux_raspbian_dists_buster_InRelease failed - 400::URIFailure (30: Read-only file system)
W: chmod 0644 of file /var/lib/apt/lists/download.docker.com_linux_raspbian_dists_buster_InRelease failed - 400::URIFailure (30: Read-only file system)
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://download.docker.com/linux/raspbian buster InRelease: Couldn't create temporary file /tmp/apt.conf.cIETDd for passing config to apt-key
W: Problem unlinking the file /var/cache/apt/pkgcache.bin - RemoveCaches (30: Read-only file system)
W: Problem unlinking the file /var/cache/apt/srcpkgcache.bin - RemoveCaches (30: Read-only file system)
pi@gladys:~ $
I think I broke everything again.
Your installation is messed up
Read-only file system
Your system is read-only, I don’t know why but you’re in for a clean installation (no DIY 
)
Edit: can you show your /boot/cmdline.txt file?
I haven’t done any DIY on Gladys as you say.
I can’t log in via SSH anymore.
I was talking about the USB installation, Gladys has nothing to do with it, your OS is not functional
From what you’re showing us, your OS is messed up, in my opinion the partition is corrupted. Then again, wasn’t this USB key experiment as well? ^^ Frankly, I’m not sure this option will work in the medium/long term. For me, a USB key is like an SD card, or even worse, in terms of lifecycle/longevity. I don’t think the manufacturer designed it to run an entire system on it, it’s made to copy files onto it, period 
Out of curiosity, what brand/model was the USB key?
Two options for you then, either you stay on your USB key and try a reinstallation (which may fail in the future, but hey if you’re a player :D), or you switch to a more durable/faster/stable disk, the best being an SSD (SSD for 17€ on Amazon in 2021, it’s worth it).
In any case, when reinstalling Gladys, remember to download the latest Raspberry Pi OS Gladys image from the website, it’s a brand new image made by @VonOx, which has nothing to do with the previous image, it’s all new
It’s a no-name one, I don’t have a case on it, just the circuit covered with a thermal sheath.
I make mini leather sleeves.
I will try again with the latest version. And if it’s not conclusive, the SSD will be preferred.
?
Otherwise yes, there are many affordable SSDs, I ordered that one myself
I am an upholsterer and decorator, and I had recovered bare 16GB and 32GB USB keys.
But I no longer have time to deal with them.
I’m not surprised you’re having problems 
Even with microSD cards, when you take « high-performance » microSD cards from a good brand, there are problems in the long term, so a no-name USB key without a brand is clearly not made for that, I’m not surprised you’re having problems.
Honestly, it’s going to be really random, even if it works for 2 weeks you risk data corruption at some point and you’ll have to reconfigure everything..
I strongly advise you to go for a more stable medium
Well, I’m reckless. I reinstalled using the new image on my USB key.
The zigbee2mqtt integration works and the sensors are detected.
I’ll see how long this lasts.