Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Outdated version #1

Open
DanielAlcon opened this issue May 18, 2020 · 6 comments
Open

Outdated version #1

DanielAlcon opened this issue May 18, 2020 · 6 comments

Comments

@DanielAlcon
Copy link

Hi are there some instructions to build a more updated version of docker-ce?

Thanks

@mforkel
Copy link
Owner

mforkel commented May 25, 2020

I'm afraid not. Have you tried to apply my patches to a more recent version of docker-ce?

@Evyde
Copy link

Evyde commented Feb 17, 2022

How can I apply patches to newer docker-ce?

@mforkel
Copy link
Owner

mforkel commented Feb 17, 2022

Basically, you might want to try to rebase the branch 18.03-i386 to a more recent branch of Docker. But I assume that will not work without further changes.

@Evyde
Copy link

Evyde commented Feb 21, 2022

Basically, you might want to try to rebase the branch 18.03-i386 to a more recent branch of Docker. But I assume that will not work without further changes.

After a few days explorering of docker, I found that there's no need to build docker-ce by myself.
The docker-ce, which is docker-cli and docker-engine, was seperated into moby/moby and docker/docker-cli since version 20.10. Both of them will not create the execuatable file docker-ce.
I guess the docker-ce command may do as what docker's do. So I just make a link between docker-ce and docker, use ln -s /usr/bin/docker-ce /usr/bin/docker. It seems works fine.
I saw somebody successfully compiled the moby outside the docker container. He just execute the command in the Dockerfile under the moby root directory.

@mforkel
Copy link
Owner

mforkel commented Feb 21, 2022

Thanks for reporting this.

@NashAqi987p
Copy link

Hello ,

I'm currently facing issues while compiling Docker CE for an i386 architecture using your mforkel/docker-ce-i386 repository. I believe your expertise can help me resolve these problems.

The problem I'm encountering happens when I run the make deb command as instructed in the repository's README. Here are the errors I'm getting:

yassine@yassine-server:~/docker-ce-i386$ make deb
make VERSION=18.03.0-ce CLI_DIR=/home/yassine/docker-ce-i386/components/cli ENGINE_DIR=/home/yassine/docker-ce-i386/components/engine -C /home/yassine/docker-ce-i386/components/packaging deb
make[1] : on entre dans le répertoire «/h ome/yassine/docker-ce-i386/components/packaging »
for p in ubuntu-xenial ubuntu-trusty debian-buster debian-stretch debian-wheezy debian-jessie raspbian-stretch raspbian-jessie; do
make -C deb VERSION=18.03.0-ce ENGINE_DIR=/home/yassine/docker-ce-i386/components/engine CLI_DIR=/home/yassine/docker-ce-i386/components/cli ${p};
done
make[2] : on entre dans le répertoire « /home/yassine/docker-ce-i386/components/packaging/deb »
docker build -t debbuild-ubuntu-xenial/i686 -f /home/yassine/docker-ce-i386/components/packaging/deb/ubuntu-xenial/Dockerfile.i686 .
unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /home/yassine/docker-ce-i386/components/packaging/deb/ubuntu-xenial/Dockerfile.i686: no such file or directory
Makefile:34: recipe for target 'ubuntu-xenial' failed
make[2]: *** [ubuntu-xenial] Error 1
make[2] : on quitte le répertoire « /home/yassine/docker-ce-i386/components/packaging/deb »
make[2] : on entre dans le répertoire « /home/yassine/docker-ce-i386/components/packaging/deb »
docker build -t debbuild-ubuntu-trusty/i686 -f /home/yassine/docker-ce-i386/components/packaging/deb/ubuntu-trusty/Dockerfile.i686 .
unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /home/yassine/docker-ce-i386/components/packaging/deb/ubuntu-trusty/Dockerfile.i686: no such file or directory
Makefile:48: recipe for target 'ubuntu-trusty' failed
make[2]: *** [ubuntu-trusty] Error 1
make[2] : on quitte le répertoire « /home/yassine/docker-ce-i386/components/packaging/deb »
make[2] : on entre dans le répertoire « /home/yassine/docker-ce-i386/components/packaging/deb »
docker build -t debbuild-debian-buster/i686 -f /home/yassine/docker-ce-i386/components/packaging/deb/debian-buster/Dockerfile.i686 .
unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /home/yassine/docker-ce-i386/components/packaging/deb/debian-buster/Dockerfile.i686: no such file or directory
Makefile:76: recipe for target 'debian-buster' failed
make[2]: *** [debian-buster] Error 1
make[2] : on quitte le répertoire « /home/yassine/docker-ce-i386/components/packaging/deb »
make[2] : on entre dans le répertoire « /home/yassine/docker-ce-i386/components/packaging/deb »
docker build -t debbuild-debian-stretch/i686 -f /home/yassine/docker-ce-i386/components/packaging/deb/debian-stretch/Dockerfile.i686 .
unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /home/yassine/docker-ce-i386/components/packaging/deb/debian-stretch/Dockerfile.i686: no such file or directory
Makefile:104: recipe for target 'debian-stretch' failed
make[2]: *** [debian-stretch] Error 1
make[2] : on quitte le répertoire « /home/yassine/docker-ce-i386/components/packaging/deb »
make[2] : on entre dans le répertoire « /home/yassine/docker-ce-i386/components/packaging/deb »
docker build -t debbuild-debian-wheezy/i686 -f /home/yassine/docker-ce-i386/components/packaging/deb/debian-wheezy/Dockerfile.i686 .
unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /home/yassine/docker-ce-i386/components/packaging/deb/debian-wheezy/Dockerfile.i686: no such file or directory
Makefile:118: recipe for target 'debian-wheezy' failed
make[2]: *** [debian-wheezy] Error 1
make[2] : on quitte le répertoire « /home/yassine/docker-ce-i386/components/packaging/deb »
make[2] : on entre dans le répertoire « /home/yassine/docker-ce-i386/components/packaging/deb »
docker build -t debbuild-debian-jessie/i686 -f /home/yassine/docker-ce-i386/components/packaging/deb/debian-jessie/Dockerfile.i686 .
unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /home/yassine/docker-ce-i386/components/packaging/deb/debian-jessie/Dockerfile.i686: no such file or directory
Makefile:90: recipe for target 'debian-jessie' failed
make[2]: *** [debian-jessie] Error 1
make[2] : on quitte le répertoire « /home/yassine/docker-ce-i386/components/packaging/deb »
make[2] : on entre dans le répertoire « /home/yassine/docker-ce-i386/components/packaging/deb »
docker build -t debbuild-raspbian-stretch/i686 -f /home/yassine/docker-ce-i386/components/packaging/deb/raspbian-stretch/Dockerfile.i686 .
unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /home/yassine/docker-ce-i386/components/packaging/deb/raspbian-stretch/Dockerfile.i686: no such file or directory
Makefile:146: recipe for target 'raspbian-stretch' failed
make[2]: *** [raspbian-stretch] Error 1
make[2] : on quitte le répertoire « /home/yassine/docker-ce-i386/components/packaging/deb »
make[2] : on entre dans le répertoire « /home/yassine/docker-ce-i386/components/packaging/deb »
docker build -t debbuild-raspbian-jessie/i686 -f /home/yassine/docker-ce-i386/components/packaging/deb/raspbian-jessie/Dockerfile.i686 .
unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /home/yassine/docker-ce-i386/components/packaging/deb/raspbian-jessie/Dockerfile.i686: no such file or directory
Makefile:132: recipe for target 'raspbian-jessie' failed
make[2]: *** [raspbian-jessie] Error 1
make[2] : on quitte le répertoire « /home/yassine/docker-ce-i386/components/packaging/deb »
Makefile:27: recipe for target 'deb' failed
make[1]: *** [deb] Error 2
make[1] : on quitte le répertoire « /home/yassine/docker-ce-i386/components/packaging »
Makefile:22: recipe for target 'deb' failed
make: *** [deb] Error 2
I've followed the README instructions carefully and I'm confident I haven't missed a step. Unfortunately, I can't seem to resolve this issue on my own.

I'm currently working on a project that requires Docker CE on an i386 architecture, and your repository seems to be the ideal resource for this task. Any assistance you can provide to resolve these issues would be greatly appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants