https://blog.stephane-robert.info/post/vagrant-wsl2-docker/

[utterances-bot]

Utiliser des boxes Vagrant Docker avec Windows Sytem Linux 2

Comment utiliser des boxes Vagrant Docker sous WSL

https://blog.stephane-robert.info/post/vagrant-wsl2-docker/

[xlhomme]

Merci pour ce tuto.

Perso lors de la creationde l'image docker , il y a des erreurs :

RUN (cd /lib/systemd/system/sysinit.target.wants/; for i in ; do [ $i == systemd-tmpfiles-setup.service ] || rm -f $i; done); \ rm -f /lib/systemd/system/multi-user.target.wants/; \ rm -f /etc/systemd/system/.wants/; \ rm -f /lib/systemd/system/local-fs.target.wants/; \ rm -f /lib/systemd/system/sockets.target.wants/udev; \ rm -f /lib/systemd/system/sockets.target.wants/initctl; \ rm -f /lib/systemd/system/basic.target.wants/; \ rm -f /lib/systemd/system/anaconda.target.wants/

---> j'ai des errerus de ce type : default: /bin/sh: 1: [: cryptsetup.target: unexpected operator default: default: /bin/sh: 1: [: dev-hugepages.mount: unexpected operator default: default: /bin/sh: 1: [: dev-mqueue.mount: unexpected operator default: default: /bin/sh: 1: [: kmod-static-nodes.service: unexpected operator default: default: /bin/sh: 1: [: proc-sys-fs-binfmt_misc.automount: unexpected operator default: default: /bin/sh: 1: [: sys-fs-fuse-connections.mount: unexpected operator default: default: /bin/sh: 1: [: sys-kernel-config.mount: unexpected operator default: default: /bin/sh: 1: [: sys-kernel-debug.mount: unexpected operator default: default: /bin/sh: 1: [: sys-kernel-tracing.mount: unexpected operator default: default: /bin/sh: 1: [: systemd-ask-password-console.path: unexpected operator default: default: /bin/sh: 1: [: systemd-binfmt.service: unexpected operator default: default: /bin/sh: 1: [: systemd-boot-system-token.service: unexpected operator default: default: /bin/sh: 1: [: systemd-journal-flush.service: unexpected operator default: default: /bin/sh: 1: [: systemd-journald.service: unexpected operator default: default: /bin/sh: 1: [: systemd-machine-id-commit.service: unexpected operator default: default: /bin/sh: 1: [: systemd-modules-load.service: unexpected operator default: default: /bin/sh: 1: [: systemd-random-seed.service: unexpected operator default: default: /bin/sh: 1: [: systemd-sysctl.service: unexpected operator default: default: /bin/sh: 1: [: systemd-sysusers.service: unexpected operator default: default: /bin/sh: 1: [: systemd-tmpfiles-setup-dev.service: unexpected operator default: default: /bin/sh: 1: [: systemd-tmpfiles-setup.service: unexpected operator default: default: /bin/sh: 1: [: systemd-update-utmp.service: unexpected operator default: default: /bin/sh: 1: [: veritysetup.target: unexpected operator default:

Je ne sais pas si c'es lié ais ensuite le container ne s'execute pas ... ==> default: Waiting for container to enter "running" state... The container started either never left the "stopped" state or very quickly reverted to the "stopped" state. This is usually because the container didn't execute a command that kept it running, and usually indicates a misconfiguration.

If you meant for this container to not remain running, please set the Docker provider configuration "remains_running" to "false":

config.vm.provider "docker" do |d| d.remains_running = false end

si tu as une idée... sinon je cherche

[stephrobert]

Bonjour,

Etrange. Vous avez bien installé et lancé le build sous Linux ?

Cdt

[Zakariasemlali]

Super intéressant, J'ai une question si vous le permettez, est-il possible d'utiliser podman comme provider à la place de docker. podman n'apparaît pas dans la liste des providers sur la doc de Vagrant Merci beaucoup pour tout ce que vous partagez sur ce blog, ainsi que sur twitter.