We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
0.10.3
The Docker Compose v2 "version: x.x" key/value pair is obsolete according to Docker's spec:
https://github.com/compose-spec/compose-spec/blob/master/spec.md#version-and-name-top-level-elements
I believe the change to the docker-compose.yml (and corresponding setup docs here https://hay-kot.github.io/homebox/quick-start/) should be the following:
Before:
version: "3.4" services: homebox: image: homebox build: context: . dockerfile: ./Dockerfile args: - COMMIT=head - BUILD_TIME=0001-01-01T00:00:00Z ports: - 3100:7745
After:
services: homebox: image: homebox build: context: . dockerfile: ./Dockerfile args: - COMMIT=head - BUILD_TIME=0001-01-01T00:00:00Z ports: - 3100:7745
Reference the Docker setup docs and docker-compose.yml file when setting up a Docker container for the first time.
Docker (Linux)
N/A
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
First Check
Homebox Version
0.10.3
What is the issue you are experiencing?
The Docker Compose v2 "version: x.x" key/value pair is obsolete according to Docker's spec:
https://github.com/compose-spec/compose-spec/blob/master/spec.md#version-and-name-top-level-elements
I believe the change to the docker-compose.yml (and corresponding setup docs here https://hay-kot.github.io/homebox/quick-start/) should be the following:
Before:
After:
How can the maintainer reproduce the issue?
Reference the Docker setup docs and docker-compose.yml file when setting up a Docker container for the first time.
Deployment
Docker (Linux)
Deployment Details
N/A
The text was updated successfully, but these errors were encountered: