Skip to main content

Docker images repository

LIDS Application Server​

warning

Since version 10, docker images for Windows are not available.

https://git.asseco-ce.com/SAMO/server/samo-lids-as-tomcat

Images are available in following variants (xx.xx.xx stands for version number):
xx.xx.xx - image for Linux containing LIDS Application Server only
For version 9 and older, also following images are available:
full-xx.xx.x - image for Linux containing LIDS Application Server + SAMO Security Manager + License Server (+ LIDS Browser in the older versions)
windows-xx.xx.xx - image for Windows Server 2019 (2016 in the older versions) containing LIDS Application Server only
windows-full-xx.xx.xx - image for Windows Server 2019 (2016 in the older versions) containing LIDS Application Server + SAMO Security Manager + License Server (+ LIDS Browser in the older versions)
windows2022-xx.xx.xx - image for Windows Server 2022 containing LIDS Application Server only
windows2022-full-xx.xx.xx - image for Windows Server 2022 containing LIDS Application Server + SAMO Security Manager + License Server (+ LIDS Browser in the older versions)

Not all Docker images from the history can be kept in this repository. They will be available according to the following rules:

Snapshots​

Only newer than 14 days are kept
📝Please, use the snapshots only internally for the testing. Don't install them at customer as most likely you'll not be able redeploy the same snaphost in the future anymore

See LIDS Application Server release notes to identify the newest version

DEV releases (currently 9.x)​

For the latest 2 minor versions – all builds are kept, e.g.:
9.11.3
9.11.2
9.11.1
9.11.0
9.10.3
9.10.2
9.10.1
9.10.0
For the older minor versions – only the latest builds are kept, e.g.:
9.9.1
9.8.0
9.7.0
9.6.x

LTS releases (currently 8.25)​

Only latest 10 are preserved, e.g. (numbers of versions are only examples, see release notes for the newest version):
8.25.31
8.25.30
8.25.29
.
.
8.25.21

⚠️Please, count with this policy in your projects⚠️

Other components (Gateway, User service, Security manager, License server, Authentication server)​

Only versions corresponding to the available LIDS Application Server versions are kept. Follow SW Components Versions and use component version which corresponds to LIDS Application Server version.

For now only these versions of components are available:
All latest builds for minor versions for major version in SAMO Platform 9
Latest build for major version in SAMO Platform 8

Storing older images on the partner side​

Because of the retention policy described above, older Docker images may no longer be available in the central repository. If you need to keep a specific build for long-term use (e.g. for a customer installation), we strongly recommend mirroring the image into your own Docker registry while it is still available.

Creating your own Docker storage​

Any standard OCI-compliant registry can be used. The most common options are:

  • GitLab Container Registry – built into every GitLab project, see the official GitLab documentation for setup.
  • Self-hosted Docker Registry – the open-source registry image can be deployed in minutes.
  • Cloud-based registries – Azure Container Registry, AWS ECR, Google Artifact Registry, Harbor, Nexus, etc.

Pushing an image to your registry​

Once your registry is ready, pull the image from the SAMO repository, re-tag it for your registry and push it:

# 1. Pull the image from the SAMO repository while it is still available
docker pull docker.asseco-ce.com/samo/server/samo-lids-as-tomcat:9.11.3

# 2. Re-tag the image for your own registry
docker tag docker.asseco-ce.com/samo/server/samo-lids-as-tomcat:9.11.3 \
    registry.example.com/samo/samo-lids-as-tomcat:9.11.3

# 3. Log in and push
docker login registry.example.com
docker push registry.example.com/samo/samo-lids-as-tomcat:9.11.3

For details on authentication and additional push options refer to the Docker CLI documentation.