You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That feels fragile, though. Are container name formats stable in docker-compose? I don't know, but it feels a little internal-API-ish. It seems like it would be better to use docker-compose itself for this:
Today, this command uses docker to exec into the compose-created
container, with an invalidly-formatted name. Instead of relying on that
format being stable (and valid), use docker-compose for it. This only
relies on the service name, which is completely under our control.
Fixplausible#245.
Signed-off-by: Kyle Fazzari <kyrofa@ubuntu.com>
Today, this command uses docker to exec into the compose-created
container, with an invalidly-formatted name. Instead of relying on that
format being stable (and valid), use docker-compose for it. This only
relies on the service name, which is completely under our control.
Fix#245.
Signed-off-by: Kyle Fazzari <kyrofa@ubuntu.com>
First of all, your self-hosting docs are excellent. That said, there's a small bug in the command provided to verify accounts:
Now, I'm using docker-compose v2.5.0. Here, the container names look like this:
Notice the hyphens versus underscores, there. A simple fix would be to simply change the docker command to use the proper container name:
That feels fragile, though. Are container name formats stable in docker-compose? I don't know, but it feels a little internal-API-ish. It seems like it would be better to use docker-compose itself for this:
The text was updated successfully, but these errors were encountered: