Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • E esap-general
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 71
    • Issues 71
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Jira
    • Jira
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • ASTRON SDC
  • ESCAPE WP5
  • esap-general
  • Issues
  • #200
Closed
Open
Issue created Oct 29, 2022 by John Swinbank@swinbankOwner

Why do we use inconsistent Python Docker images?

  • esap-api-gateway's esap/Dockerfile says FROM python:3.10-slim.
  • esap-api-gateway's .gitlab-ci.yml uses image: python:latest for run-unit-tests.
  • esap-worker's Dockerfile starts with FROM python:3.10-alpine.

Somebody on the internet told me that using Alpine is a bad idea (but I didn't actually test for myself). Regardless of that, though, it seems like we should be consistent everywhere unless there's a reason not to be. And we definitely don't want to be testing with a version of Python (3.11) that's different from the version we're developing with (3.10), which means we should likely never using anything :latest.

Assignee
Assign to
Time tracking