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

Push environments to ghcr.io and docker.io #60

Closed
2 of 3 tasks
bryanhonof opened this issue Nov 6, 2024 · 4 comments
Closed
2 of 3 tasks

Push environments to ghcr.io and docker.io #60

bryanhonof opened this issue Nov 6, 2024 · 4 comments
Assignees
Labels
team-content Issues to be picked up by @flox/team-content team-developer-support Issues to be picked up by @flox/team-developer-support

Comments

@bryanhonof
Copy link
Member

bryanhonof commented Nov 6, 2024

We'd like for these example environments to be pushed to the ghcr.io and docker.io container registries. This will require us to first turn these Flox environments into containers with something like flox containerize.

Acceptance Criteria

  • There must be a workflow that automatically turns these example environments into containers
  • The resulting containers must be pushed to ghcr.io
  • The resulting containers may be pushed to docker.io
@bryanhonof bryanhonof added the team-developer-support Issues to be picked up by @flox/team-developer-support label Nov 6, 2024
@floxbot floxbot added the team-content Issues to be picked up by @flox/team-content label Nov 6, 2024
@bryanhonof bryanhonof changed the title Push floxenvs to ghcr.io and docker.io Push environments to ghcr.io and docker.io Nov 6, 2024
@tomberek
Copy link
Contributor

tomberek commented Nov 7, 2024

@bryanhonof
Copy link
Member Author

It seems that flox containerize doesn't start services automatically when starting a container. So, we can get the automation in place, but the containers themselves won't be as nice to use until we address the aforementioned issue.

@tomberek
Copy link
Contributor

tomberek commented Nov 8, 2024

Thanks... then we need to see what possibilities there are. Can we install flox itself into the envs... start watchdog/process-compose that way?

@bryanhonof bryanhonof self-assigned this Nov 18, 2024
@garbas garbas assigned garbas and unassigned bryanhonof Nov 20, 2024
@garbas
Copy link
Contributor

garbas commented Nov 20, 2024

@stahnma I think we should skip pushing to docker.io since we are also not pushing flox docker image there.

@stahnma stahnma closed this as completed Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team-content Issues to be picked up by @flox/team-content team-developer-support Issues to be picked up by @flox/team-developer-support
Projects
None yet
Development

No branches or pull requests

5 participants