You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running invoke db-export within the nautobot-docker-compose project, the command fails due to warnings about deprecated version fields in YAML configuration files and a service naming error indicating "no such service: postgres."
Steps to Reproduce
Clone the nautobot-docker-compose repository.
Navigate to the project directory.
Execute the command invoke db-export.
Expected Behavior
The database export process should execute without errors, properly identifying the correct database service name and avoiding any deprecated warnings.
Actual Behavior
The following issues were encountered:
Obsolete version field warnings in docker-compose.postgres.yml, docker-compose.base.yml, and docker-compose.local.yml.
Error message: "no such service: postgres".
It was noted that the actual database service is named db and not postgres, as evidenced by docker ps output.
Possible Fix
Modify the tasks.py file to reference the correct service name (db instead of postgres).
Review and update the Docker Compose YAML files to comply with current Docker standards, specifically removing or updating the deprecated version field.
Additional Information
It may be necessary to confirm the database service configuration to ensure the service is intended to use PostgreSQL and not MySQL, as inferred by the use of the postgres:13-alpine image.
The text was updated successfully, but these errors were encountered:
Description
When running
invoke db-export
within the nautobot-docker-compose project, the command fails due to warnings about deprecatedversion
fields in YAML configuration files and a service naming error indicating "no such service: postgres."Steps to Reproduce
invoke db-export
.Expected Behavior
The database export process should execute without errors, properly identifying the correct database service name and avoiding any deprecated warnings.
Actual Behavior
The following issues were encountered:
version
field warnings indocker-compose.postgres.yml
,docker-compose.base.yml
, anddocker-compose.local.yml
.It was noted that the actual database service is named
db
and notpostgres
, as evidenced bydocker ps
output.Possible Fix
tasks.py
file to reference the correct service name (db
instead ofpostgres
).version
field.Additional Information
postgres:13-alpine
image.The text was updated successfully, but these errors were encountered: