Skip to content

Update docker-compose.yml: Remove top-level version element #8555

Description

@abinetabate1

Prerequisites

  1. Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our Getting Started page and attend an onboarding session.
  2. You have already read our How to Contribute to Hack for LA Guide.

Overview

We need to update docker-compose.yml so that a warning is not displayed when running docker-compose up

Action Items

  • Run docker-compose up and observe that a warning similar to the one shown below is displayed.
$ docker-compose up
time="2026-03-15T08:28:12-07:00" level=warning msg="C:\\code\\hfla\\website\\docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion"
  • In your IDE, open the docker-compose.yml file.
  • Find the top-level version property and remove it. It is the first line in the file.
version: "3"

  • Verify that the warning is no longer displaying when running docker-compose up. Include before and after screenshots with your pull request.

Resources/Instructions

  1. docker-compose.yml
  2. Info about top-level version element

Activity

  1. github-actions commented on Mar 15, 2026

    @github-actions
  2. 35 remaining items

  3. hfla-graphql-app commented on Jun 19, 2026

    @hfla-graphql-app

    Hello @abinetabate1!

    Please add an update comment using the below template (even if you have a pull request). Afterwards, remove
    the status: 2 Weeks Inactive label and add the status: Updated label.

    1. Progress: What is the current status of your issue? What have you completed and what is left to do?
    2. Blockers: Explain any difficulties or errors encountered.
    3. Availability: How much time will you have this week to work on this issue?
    4. ETA: When do you expect this issue to be completed?
    5. Pictures (optional): Add any pictures of the visual changes made to the site so far.

    If you need help, be sure to either: 1) place your issue in the "Questions / In Review" status column of the
    Project Board and ask for help at your next meeting; 2) put a status: Help Wanted label on your issue
    and pull request; or 3) put up a request for assistance on the team's hfla-site Slack channel.

    Please note that including your questions in the issue comments- along with screenshots, if applicable-
    will help us to help you. Here and here are examples of well-formed questions.

    You are receiving this comment because your last comment was before 06/05/2026, 01:44 AM PDT.

  4. hfla-graphql-app commented on Jun 26, 2026

    @hfla-graphql-app

    Hello @abinetabate1!

    Please add an update comment using the below template (even if you have a pull request). Afterwards, remove
    the status: 2 Weeks Inactive label and add the status: Updated label.

    1. Progress: What is the current status of your issue? What have you completed and what is left to do?
    2. Blockers: Explain any difficulties or errors encountered.
    3. Availability: How much time will you have this week to work on this issue?
    4. ETA: When do you expect this issue to be completed?
    5. Pictures (optional): Add any pictures of the visual changes made to the site so far.

    If you need help, be sure to either: 1) place your issue in the "Questions / In Review" status column of the
    Project Board and ask for help at your next meeting; 2) put a status: Help Wanted label on your issue
    and pull request; or 3) put up a request for assistance on the team's hfla-site Slack channel.

    Please note that including your questions in the issue comments- along with screenshots, if applicable-
    will help us to help you. Here and here are examples of well-formed questions.

    You are receiving this comment because your last comment was before 06/12/2026, 01:10 AM PDT.

  5. hfla-graphql-app commented on Aug 7, 2026

    @hfla-graphql-app
  6. hfla-graphql-app commented on Aug 14, 2026

    @hfla-graphql-app
  7. hfla-graphql-app commented on Aug 21, 2026

    @hfla-graphql-app
  8. hfla-graphql-app commented on Aug 28, 2026

    @hfla-graphql-app
  9. hfla-graphql-app commented on Sep 4, 2026

    @hfla-graphql-app
  10. hfla-graphql-app commented on Sep 11, 2026

    @hfla-graphql-app
  11. hfla-graphql-app commented on Sep 18, 2026

    @hfla-graphql-app
  12. hfla-graphql-app commented on Sep 25, 2026

    @hfla-graphql-app

    Hello @abinetabate1-

    Please add an update using the below template (even if you have a pull request). Afterwards, remove
    the status: 2 Weeks Inactive label and add the status: Updated label.

    1. Progress: What is the current status of this issue? What have you completed and what is left to do?
    2. Blockers: Explain any difficulties or errors encountered.
    3. Availability: How much time will you have this week to work on this issue?
    4. ETA: When do you expect this issue to be completed?
    5. Pictures (optional): Add any pictures of the visual changes made to the site so far.

    If you need help, be sure to either: 1) place your issue in the "Questions / In Review" status-column of the
    Project Board and ask for help at your next meeting; 2) put a status: Help Wanted label on your issue
    and pull request; or 3) put up a request for assistance on the team's hfla-site Slack channel.

    Please note that including your questions in the issue comments- along with screenshots, if applicable-
    will help us to help you. Here and here are examples of well-formed questions.

    You are receiving this comment because your last update was before 09/11/2026, 12:04 AM PDT PST.

  13. yielderdev commented on Sep 30, 2026

    @yielderdev
    Member

    Hi @abinetabate1

    Given the date of last activity on this issue, I will be unassigning you unless we hear from you within seven days.

  14. hfla-graphql-app commented on Oct 2, 2026

    @hfla-graphql-app

    Hello @abinetabate1-

    Please add an update using the below template (even if you have a pull request). Afterwards, remove
    the status: 2 Weeks Inactive label and add the status: Updated label.

    1. Progress: What is the current status of this issue? What have you completed and what is left to do?
    2. Blockers: Explain any difficulties or errors encountered.
    3. Availability: How much time will you have this week to work on this issue?
    4. ETA: When do you expect this issue to be completed?
    5. Pictures (optional): Add any pictures of the visual changes made to the site so far.

    If you need help, be sure to either: 1) place your issue in the "Questions / In Review" status-column of the
    Project Board and ask for help at your next meeting; 2) put a status: Help Wanted label on your issue
    and pull request; or 3) put up a request for assistance on the team's hfla-site Slack channel.

    Please note that including your questions in the issue comments- along with screenshots, if applicable-
    will help us to help you. Here and here are examples of well-formed questions.

    You are receiving this comment because your last update was before 09/18/2026, 12:07 AM PDT PST.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions