-
Notifications
You must be signed in to change notification settings - Fork 1
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
ENP Docker overhaul #125
Comments
Need to re-evaluate if necessary. |
QA Conversation
|
At the start of this ticket:
|
Do you have the api database running when running |
I did not have the notification-api database running, but running it first doesn't clear the error.
|
I found what seems to be an easy solution to the above traceback. In .env.docker, I changed "host.docker.internal", which is not valid on Linux (probably because Docker Desktop isn't intalled), in the API database connection string to "ci-db-1" , which resolves because all the running containers are in the "ci_default" network. |
The branch is deployed, and routes seem to work with Postman. QA tells me she is happy with it. I didn't see anything in the GHA ticket to lead me to believe there are any additional problems I need to address. |
PR Approved and Merged. Tested locally by pulling down the code, and walking through the wiki to...
Tested in the Cloud by deploying to Perf
|
User Story - Business Need
Whilst performing other work, there appear to be problems with the way the container is Dockerized. This ticket aims to overhaul that container and documentation.
User Story(ies)
As a VA ENP dev
I want a consistent, repeatable Docker container
So that development is simplified
Additional Info and Resources
Issue 1: the Poetry version is pinned down to 1.8.3 when we upgraded to 1.8.4 within the last three months.

Issue 2: Kyle had issues running the existing container (see him for details).
Issue 3: bash is not in the Docker build but the script runs bash
Acceptance Criteria
QA Considerations
Potential Dependencies
The text was updated successfully, but these errors were encountered: