You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
Once #2234 and LiskArchive/lisk-docker#100 are merged we will have one Dockerfile and one docker-compose.yml as well as the ability to run any network configuration with the -n switch. Under those conditions it makes sense to move the docker-compose.yml file from the LiskHQ/lisk-docker repository to LiskHQ/lisk.
Actual behavior
For historical reasons docker-compose.yml is hosted at LiskHQ/lisk-docker just like the Dockerfile used to be.
Steps to reproduce
Look at both LiskHQ/lisk and LiskHQ/lisk-docker repositories.
Which version(s) does this affect? (Environment, OS, etc...)
Docker using lisk core >= 1.1
The text was updated successfully, but these errors were encountered:
Expected behavior
Once #2234 and LiskArchive/lisk-docker#100 are merged we will have one
Dockerfile
and onedocker-compose.yml
as well as the ability to run any network configuration with the-n
switch. Under those conditions it makes sense to move thedocker-compose.yml
file from the LiskHQ/lisk-docker repository to LiskHQ/lisk.Actual behavior
For historical reasons
docker-compose.yml
is hosted at LiskHQ/lisk-docker just like theDockerfile
used to be.Steps to reproduce
Look at both LiskHQ/lisk and LiskHQ/lisk-docker repositories.
Which version(s) does this affect? (Environment, OS, etc...)
Docker using lisk core >= 1.1
The text was updated successfully, but these errors were encountered: