Problem with using self-built GDAL in Docker

By -

I am trying to prepare an Ubuntu 22.04 Docker image with GDAL 3.2.2. This GDAL installation needs to have ECW support, which means I cannot use the pre-built gdal-bin package that can be installed using apt.

I can build and install GDAL with these specs in the Docker container. But when running a simple test command on a simple tiff file I get an error that I have no idea how to debug.

$ gdalinfo --version
GDAL 3.2.2, released 2021/03/05
$ gdalinfo test.tif
Driver: GTiff/GeoTIFF
Files: test.tif
Size is 572, 577
Aborted (core dumped)

The steps I took was starting with a regular Ubuntu 22.04 Docker image. Installing prerequisites (gcc and stuff). Downloading the ECW SDK. Install that. Download the source of gdal 3.2.2. Configure the build to include ECW. Use the make file to build and then install.

If I do not use a self-built GDAL but rather install gdal-bin using apt directly, it works for the tiff file, but it would mean I have no ECW support.

I have also successfully built and used GDAL with ECW directly on Ubuntu 22.04 without Docker.

Does anyone know a solution for this or have any idea in which direction I could look to potentially debug it?



Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more