Closed Sam-R closed 1 year ago
Oh you're right about the tag! I'll check for the containers names.
I superseded your PR changes for the version with https://github.com/acouvreur/sablier/pull/138.
Can you rebase on it once merged ?
And we should probably use container names instead of the auto assigned docker-compose ones.
What do you think?
Sure, I've rebased and the PR is now up to date with main.
I tend to avoid specific container names in my environments because it impacts dockers ability to scale. For the quick-start it might be okay but I wouldn't normally run named containers in pre-prod/prod.
Are you seeing different docker container name formats? I wasn't sure if that'd be the case which is why I listed my docker version and OS version.
:tada: This PR is included in version 1.4.0 :tada:
The release is available on:
v1.4.0
Your semantic-release bot :package::rocket:
Minor fixes to the
docker-compose.yml
file based on the quick-start instructions inREADME.md
.acouvreur/sablier:1.3.0
as per dockerhub's tag to solveERROR: manifest for acouvreur/sablier:v1.3.0 not found: manifest unknown: manifest unknown
message ondocker-compose up -d
.An error occured: Error: No such container: sablier-whoami-1
error when calling the dynamic URL in a web browser.