Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

./examples/tutorial.sh is broken #78

Open
emk opened this issue Oct 18, 2017 · 4 comments
Open

./examples/tutorial.sh is broken #78

emk opened this issue Oct 18, 2017 · 4 comments
Milestone

Comments

@emk
Copy link
Contributor

emk commented Oct 18, 2017

beta is failing because it runs one important test that stable skips. To run this locally, run:

cd cage
cargo install -f
./examples/tutorial.sh

I'm investigating, but please feel free to take a look if you want.

CC @camjackson

@emk
Copy link
Contributor Author

emk commented Oct 18, 2017

From the logs:

waiting for server to start....2017-10-18 16:00:26.569 UTC [41] FATAL:  data directory "/var/lib/postgresql/data" has group or world access
2017-10-18 16:00:26.569 UTC [41] DETAIL:  Permissions should be u=rwx (0700).
 stopped waiting
pg_ctl: could not start server
Examine the log output.

Looks like cage new is producing broken output, probably because https://github.com/faradayio/cage/blob/master/data/templates/new/pods/db.yml is not setting up a working set of directory permissions. Not sure how easy this will be to fix.

@emk emk closed this as completed in 06691e5 Oct 18, 2017
@emk emk added this to the v0.2.3 milestone Oct 18, 2017
@emk
Copy link
Contributor Author

emk commented Oct 18, 2017

OK, the underlying problem here is actually with the standard Docker postgres containers. They no longer reliably allow you to mount newly-created named volumes. I've switched to the Alpine version of the PostgreSQL container, which seems to work a bit better, but may not be a complete fix.

@emk emk reopened this Oct 18, 2017
@camjackson
Copy link
Contributor

That seems like a pretty big limitation :/

Is there an open issue somewhere where that's being discussed?

@emk
Copy link
Contributor Author

emk commented Oct 19, 2017

I've seen a couple different issues on various PG Docker containers, but I haven't actually found the repo for the official upstream container.

Given that this issue existed with 0.2.2, for a while, and that it's going to take some time to fix, I'm going to release 0.2.3 anyway and get the other fixes out, and bump this to 0.2.4.

@emk emk modified the milestones: v0.2.3, v0.2.4 Oct 19, 2017
@emk emk modified the milestones: v0.2.4, v0.3.0 Apr 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants