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

Use a registry for storing docker frontend image #57

Merged
merged 1 commit into from
Jul 4, 2023
Merged

Conversation

lyrixx
Copy link
Member

@lyrixx lyrixx commented Jun 29, 2023

No description provided.

@lyrixx lyrixx force-pushed the registry branch 30 times, most recently from 37d1e9f to c733b08 Compare July 1, 2023 13:35
@lyrixx lyrixx force-pushed the registry branch 2 times, most recently from 0e8264b to a1501c8 Compare July 1, 2023 13:39
}

function docker_compose_run(
string $runCommand,
Context $c = null,
string $service = 'builder',
string $user = 'app',
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not possible to exec something with something else than app. Anyway, we never changed this value, right?

Comment on lines +12 to +15
# cache_to:
# - "ghcr.io/jolicode/monologue/builder:${BUILDER_VERSION:-latest}"
# cache_from:
# - "ghcr.io/jolicode/monologue/builder:${BUILDER_VERSION:-latest}"
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we want, we can share the cache on the registry. Not sure it's useful tho

@@ -29,7 +41,7 @@ services:
- "traefik.http.routers.${PROJECT_NAME}-frontend-unsecure.middlewares=redirect-to-https@file"

postgres:
build: services/postgres
image: postgres:15.2
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Avoid pushing an extra image to the registry

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file will update the linux user ID at runtime:

  • if I publish an image, the image will contain my user id (usually 1000)
  • Then if someone else (let's say GA) runs with another user id (let's say 1001), the permission will be wrong (host = 1001, container = 1000).

So this entry point will update the app user id in the container, to match the one on the host.

https://stackoverflow.com/a/66455612/685587

@lyrixx lyrixx force-pushed the registry branch 2 times, most recently from a9fc149 to 5e1167d Compare July 1, 2023 14:10
@lyrixx lyrixx merged commit 61cc359 into main Jul 4, 2023
1 check passed
@lyrixx lyrixx deleted the registry branch July 4, 2023 12:43
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

Successfully merging this pull request may close these issues.

2 participants