Hi all, Upgrade to v0.10 with command : docker pull acryldata/datahub-upgrade:head && docker run acryldata/datahub-upgrade:head -u NoCodeDataMigration Got error : Status: Image is up to date for acryldata/datahub-upgrade:head docker.io/acryldata/datahub-upgrade:head ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console...

The no code data migration is no going to upgrade datahub, it runs data migration after datahub is running for no code. How are you running DataHub ? Using quickstart or helm charts? Depending which method, I can recommend the correct upgrade process for you.

Hi @brainy-tent-14503 we are running in v0.9.5 with a quickstart docker compose method. Thanks for your help. Rgds. Bruno

With quickstart, by default, it will follow the latest changes in master branch and use docker head images. Since you specified

v0.9.5

are you using the override flag

--version v0.9.5

? I would suggest this method, first update the python cli, from docs.

python3 -m pip install --upgrade pip wheel setuptools
python3 -m pip install --upgrade acryl-datahub
# validate that the install was successful
datahub version

# should look somthing like this
$ datahub version
DataHub CLI version: 0.10.0
Python version: 3.10.8 (main, Oct 13 2022, 09:48:40) [Clang 14.0.0 (clang-1400.0.29.102)]

Next run quickstart with this command

datahub quickstart --version v0.10.0

Hi @brainy-tent-14503 in fact I use docker-compose as datahub quickstart cmd doesnt'find docker 🙂

It is looking for the docker socket here - https://github.com/datahub-project/datahub/blob/master/metadata-ingestion/src/datahub/cli/docker_check.py#L86

There is no .docker/run folder ! coming from docker desktop I think (base) C:\Users\JB6407>docker info Client: Context: default Debug Mode: false Plugins: buildx: Docker Buildx (Docker Inc., v0.9.1) compose: Docker Compose (Docker Inc., v2.13.0) dev: Docker Dev Environments (Docker Inc., v0.0.5) extension: Manages Docker extensions (Docker Inc., v0.2.16) sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc., 0.6.0) scan: Docker Scan (Docker Inc., v0.22.0) Server: Containers: 22 Running: 1 Paused: 0 Stopped: 21 Images: 65 Server Version: 20.10.21 Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Native Overlay Diff: true userxattr: false Logging Driver: json-file Cgroup Driver: cgroupfs Cgroup Version: 1 Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog Swarm: inactive Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc Default Runtime: runc Init Binary: docker-init containerd version: 770bd0108c32f3fb5c73ae1264f7e503fe7b2661 runc version: v1.1.4-0-g5fd4c4d init version: de40ad0 Security Options: seccomp Profile: default Kernel Version: 5.10.102.1-microsoft-standard-WSL2 Operating System: Docker Desktop OSType: linux Architecture: x86_64 CPUs: 12 Total Memory: 24.86GiB Name: docker-desktop ID: ATMCUBUOP4KQLX3YOWYWZQ5UPDOAFPERGUPZMIXAHZQM:LIYA Docker Root Dir: /var/lib/docker Debug Mode: false HTTP Proxy: http.docker.internal:3128 HTTPS Proxy: http.docker.internal:3128 No Proxy: hubproxy.docker.internal Registry: https://index.docker.io/v1/ Labels: Experimental: false Insecure Registries: hubproxy.docker.internal:5000 127.0.0.0/8 Live Restore Enabled: false WARNING: No blkio throttle.read_bps_device support WARNING: No blkio throttle.write_bps_device support WARNING: No blkio throttle.read_iops_device support WARNING: No blkio throttle.write_iops_device support

Based on

C:\Users\JB6407

, it appears that you are using Windows. I am not sure if this is a supported platform, however it would explain why it can’t find the expected unix socket. You might have to figure out some workarounds, maybe this so thread…

Hi @brainy-tent-14503 yes it's a local install for a POC, you can close the case, in the future we will use a k8s cluster. Thanks.