-
Notifications
You must be signed in to change notification settings - Fork 6
Open
Description
Hello, I'm trying to build a custom Lokinet exit node image using Docker, but the build process fails because it cannot reach the registry.oxen.rocks/lokinet-exit:latest image. The error message indicates that the image cannot be found or resolved.
Steps to Reproduce:
- Attempted to build a custom Lokinet exit node image using Docker Compose.
- Set up the Dockerfile and necessary configurations.
- Ran the build command.
Error Message:
[BUILD] Building custom Lokinet exit node image...
Compose can now delegate builds to bake for better performance.
To do so, set COMPOSE_BAKE=true.
[+] Building 1.5s (2/2) FINISHED docker:desktop-linux
=> [lokinet internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 161B 0.0s
=> ERROR [lokinet internal] load metadata for registry.oxen.rocks/lokinet-exit:latest 1.4s
------
> [lokinet internal] load metadata for registry.oxen.rocks/lokinet-exit:latest:
------
failed to solve: registry.oxen.rocks/lokinet-exit:latest: failed to resolve source metadata for registry.oxen.rocks/lokinet-exit:latest: registry.oxen.rocks/lokinet-exit:latest: not found
[ERROR] Failed to build Lokinet image!Expected Behavior:
The build process should successfully load the metadata for the lokinet-exit image and proceed with the build.
Actual Behavior:
The build process fails with an error indicating that the metadata for registry.oxen.rocks/lokinet-exit:latest could not be resolved.
Dockerfile
FROM registry.oxen.rocks/lokinet-exit:latest
RUN /bin/bash -c 'ln -s /var/lib/lokinet/conf.d/custom.ini /data/custom.ini'docker-compose.yml
services:
lokinet:
build: .
privileged: true
tty: true
tmpfs:
- /run
- /tmp
volumes:
- /sys/fs/cgroup:/sys/fs/cgroup:ro
- /sys/fs/cgroup/systemd
- data:/data
volumes:
data:Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels