Create Repo failing
Bonsaikitt3n opened this issue · 5 comments
AWS client and access are working with the right perms.
WP Snapshots configuration verified and saved.
octagon@hax ~/c/w/updato-test> 10updocker wpsnapshots create-repository dood
Ensuring global network exists
- Network exists
Ensuring global cache volume exists - Creating Volume
Ensuring global services are running
global_mailcatcher_1 is up-to-date
global_dns_1 is up-to-date
global_mysql_1 is up-to-date
global_gateway_1 is up-to-date
global_phpmyadmin_1 is up-to-date
Waiting for mysql...
Checking USER ID
Host user is 0:0
The "--db_user" option does not exist.
create-repository
octagon@hax ~/c/w/updato-test>
@Bonsaikitt3n this appears to be an issue with WP Local Docker. For you, you could try setting up the repo on your host machine composer global require 10up/wpsnapshots.
@cmmarslender mind taking a look? I get that same error when I run 10updocker wpsnapshots -v
The vanilla install of wpsnapshots seems to create repo. I'm guessing the issue is in:
If I have a sec I will test what happens with the --db_user=root taken out of that command
Nope, I lied. S3 bucket was created in us-west-1, failed silently on the dynamoDB create table. The command did go through though and said repo created. Maybe have a check at the end that the resources actually exist.
Sorry, being so chatty in here. Turns out the dynamoDB failure was because of the state of the current existing repo and the failures of using this with the 10updocker v2. I went back with the vanilla client and re-created the original repo name and created the dynamo resource. This thing gets in weird states if there is that error caused by the v2 wrapper.
The WP Local Docker issues are resolved in version 2.4.3 ( 10up/wp-local-docker-v2@6ba0d74 )