this is what I thought would be the case.. you have to look into your sshd_config configuration.. I would probably go simpler and use, username and password for packer-->VM authentication.. and get simple sshd_config configuration to be installed in the VM...
*2021/02/09 06:31:35 packer-builder-vmware-iso plugin: [DEBUG] SSH handshake err: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none], no supported methods remain* this to me potentially indicates that packer do not know how to use the certificate.. but without seeing the actual sshd_config to be copy in the VM will be imposible for me to tell.. here is one issue which looks similar to your issue https://github.com/hashicorp/packer/issues/8750 On Tuesday, February 9, 2021 at 11:16:23 AM UTC+1 [email protected] wrote: > I set a static up for the VM and could access it via ssh, but packer > outputs SSH the error below: > > 2021/02/09 06:31:28 packer-builder-vmware-iso plugin: [DEBUG] Detected > authentication error. Increasing handshake attempts. > 2021/02/09 06:31:35 packer-builder-vmware-iso plugin: [INFO] Attempting > SSH connection to redacted... > 2021/02/09 06:31:35 packer-builder-vmware-iso plugin: [DEBUG] reconnecting > to TCP connection for SSH > 2021/02/09 06:31:35 packer-builder-vmware-iso plugin: [DEBUG] handshaking > with SSH > 2021/02/09 06:31:35 packer-builder-vmware-iso plugin: [DEBUG] SSH > handshake err: ssh: handshake failed: ssh: unable to authenticate, > attempted method > s [none], no supported methods remain > > This the log when I connect via ssh: > > $ ssh -i sshkeys/id_rsa core@redacted -vvvv > OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017 > debug1: Reading configuration data /home/mpires/.ssh/config > debug1: Reading configuration data /etc/ssh/ssh_config > debug1: /etc/ssh/ssh_config line 19: Applying options for * > debug2: resolving "redacted" port 22 > debug2: ssh_connect_direct: needpriv 0 > debug1: Connecting to redacted [redacted] port 22. > debug1: Connection established. > debug1: identity file sshkeys/id_rsa type 0 > debug1: key_load_public: No such file or directory > debug1: identity file sshkeys/id_rsa-cert type -1 > debug1: Local version string SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 > debug1: Remote protocol version 2.0, remote software version OpenSSH_8.1 > debug1: match: OpenSSH_8.1 pat OpenSSH* compat 0x04000000 > debug2: fd 3 setting O_NONBLOCK > debug1: Authenticating to 10.127.152.55:22 as 'core' > debug3: hostkeys_foreach: reading file "/home/mpires/.ssh/known_hosts" > debug3: record_hostkey: found key type ECDSA in file > /home/mpires/.ssh/known_hosts:121 > debug3: load_hostkeys: loaded 1 keys from 10.127.152.55 > debug3: order_hostkeyalgs: prefer hostkeyalgs: > [email protected],[email protected] > ,ecdsa-sha2-nistp521- > [email protected],ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521 > > > debug3: send packet: type 20 > debug1: SSH2_MSG_KEXINIT sent > debug3: receive packet: type 20 > debug1: SSH2_MSG_KEXINIT received > debug2: local client KEXINIT proposal > debug2: KEX algorithms: curve25519-sha256,[email protected] > ,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group- > > exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha256,diffie-h > ellman-group14-sha1,ext-info-c > debug2: host key algorithms: [email protected], > [email protected],[email protected] > om,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521, > [email protected],[email protected],ssh-ed25519,rsa-sha2-512 > ,rsa-sha2-256,ssh-rsa > debug2: ciphers ctos: [email protected] > ,aes128-ctr,aes192-ctr,aes256-ctr,[email protected], > [email protected] > debug2: ciphers stoc: [email protected] > ,aes128-ctr,aes192-ctr,aes256-ctr,[email protected], > [email protected] > debug2: MACs ctos: [email protected],[email protected], > [email protected],[email protected],hmac-sha1-etm@openssh > .com,[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1 > > > debug2: MACs stoc: [email protected],[email protected], > [email protected],[email protected],hmac-sha1-etm@openssh > .com,[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1 > > > debug2: compression ctos: none,[email protected],zlib > debug2: compression stoc: none,[email protected],zlib > debug2: languages ctos: > debug2: languages stoc: > debug2: first_kex_follows 0 > debug2: reserved 0 > debug2: peer server KEXINIT proposal > debug2: KEX algorithms: curve25519-sha256,[email protected] > ,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group- > exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1 > > > debug2: host key algorithms: > rsa-sha2-512,rsa-sha2-256,ssh-rsa,ecdsa-sha2-nistp256,ssh-ed25519 > debug2: ciphers ctos: [email protected] > ,aes128-ctr,aes192-ctr,aes256-ctr,[email protected], > [email protected] > debug2: ciphers stoc: [email protected] > ,aes128-ctr,aes192-ctr,aes256-ctr,[email protected], > [email protected] > debug2: MACs ctos: [email protected],[email protected], > [email protected],[email protected],hmac-sha1-etm@openssh > .com,[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1 > > > debug2: MACs stoc: [email protected],[email protected], > [email protected],[email protected],hmac-sha1-etm@openssh > .com,[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1 > > > debug2: compression ctos: none,[email protected] > debug2: compression stoc: none,[email protected] > debug2: languages ctos: > debug2: languages stoc: > debug2: first_kex_follows 0 > debug2: reserved 0 > debug1: kex: algorithm: curve25519-sha256 > debug1: kex: host key algorithm: ecdsa-sha2-nistp256 > debug1: kex: server->client cipher: [email protected] MAC: > <implicit> compression: none > debug1: kex: client->server cipher: [email protected] MAC: > <implicit> compression: none > debug3: send packet: type 30 > debug1: expecting SSH2_MSG_KEX_ECDH_REPLY > debug3: receive packet: type 31 > debug1: Server host key: ecdsa-sha2-nistp256 SHA256:redacted > debug3: hostkeys_foreach: reading file "/home/mpires/.ssh/known_hosts" > debug3: record_hostkey: found key type ECDSA in file > /home/mpires/.ssh/known_hosts:121 > debug3: load_hostkeys: loaded 1 keys from 10.127.152.55 > debug1: Host '10.127.152.55' is known and matches the ECDSA host key. > debug1: Found key in /home/mpires/.ssh/known_hosts:121 > debug3: send packet: type 21 > debug2: set_newkeys: mode 1 > debug1: rekey after 134217728 blocks > debug1: SSH2_MSG_NEWKEYS sent > debug1: expecting SSH2_MSG_NEWKEYS > debug3: receive packet: type 21 > debug1: SSH2_MSG_NEWKEYS received > debug2: set_newkeys: mode 0 > debug1: rekey after 134217728 blocks > debug2: key: sshkeys/id_rsa (0x559105ef1d90), explicit > debug3: send packet: type 5 > debug3: receive packet: type 7 > debug1: SSH2_MSG_EXT_INFO received > debug1: kex_input_ext_info: > server-sig-algs=<ssh-ed25519,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2 > -nistp521> > debug3: receive packet: type 6 > debug2: service_accept: ssh-userauth > debug1: SSH2_MSG_SERVICE_ACCEPT received > debug3: send packet: type 50 > debug3: receive packet: type 51 > debug1: Authentications that can continue: > publickey,password,keyboard-interactive > debug3: start over, passed a different list > publickey,password,keyboard-interactive > debug3: preferred > gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive,password > debug3: authmethod_lookup publickey > debug3: remaining preferred: keyboard-interactive,password > debug3: authmethod_is_enabled publickey > debug1: Next authentication method: publickey > debug1: Offering public key: RSA redacted sshkeys/id_rsa > debug3: send_pubkey_test > debug3: send packet: type 50 > debug2: we sent a publickey packet, wait for reply > debug3: receive packet: type 60 > debug1: Server accepts key: pkalg rsa-sha2-512 blen 407 > debug2: input_userauth_pk_ok: fp SHA256:redacted > debug3: sign_and_send_pubkey: RSA SHA256:redacted > debug3: send packet: type 50 > debug3: receive packet: type 52 > debug1: Authentication succeeded (publickey). > Authenticated to 10.127.152.55 ([10.127.152.55]:22). > debug1: channel 0: new [client-session] > debug3: ssh_session2_open: channel_new: 0 > debug2: channel 0: send open > debug3: send packet: type 90 > debug1: Requesting [email protected] > debug3: send packet: type 80 > debug1: Entering interactive session. > debug1: pledge: network > debug3: receive packet: type 80 > debug1: client_input_global_request: rtype [email protected] > want_reply 0 > debug3: receive packet: type 4 > debug1: Remote: /home/core/.ssh/authorized_keys:1: key options: > agent-forwarding port-forwarding pty user-rc x11-forwarding > debug3: receive packet: type 4 > debug1: Remote: /home/core/.ssh/authorized_keys:1: key options: > agent-forwarding port-forwarding pty user-rc x11-forwarding > debug3: receive packet: type 91 > debug2: channel_input_open_confirmation: channel 0: callback start > debug2: fd 3 setting TCP_NODELAY > debug3: ssh_packet_set_tos: set IP_TOS 0x10 > debug2: client_session2_setup: id 0 > debug2: channel 0: request pty-req confirm 1 > debug3: send packet: type 98 > debug1: Sending environment. > debug3: Ignored env COLORFGBG > debug3: Ignored env COLORTERM > debug3: Ignored env DBUS_SESSION_BUS_ADDRESS > debug3: Ignored env DEFAULTS_PATH > debug3: Ignored env DESKTOP_SESSION > debug3: Ignored env DISPLAY > debug3: Ignored env GPG_AGENT_INFO > debug3: Ignored env GS_LIB > debug3: Ignored env GTK_MODULES > debug3: Ignored env HOME > debug3: Ignored env KDE_FULL_SESSION > debug3: Ignored env KDE_SESSION_UID > debug3: Ignored env KDE_SESSION_VERSION > debug3: Ignored env KONSOLE_DBUS_SERVICE > debug3: Ignored env KONSOLE_DBUS_SESSION > debug3: Ignored env KONSOLE_DBUS_WINDOW > debug3: Ignored env KONSOLE_PROFILE_NAME > debug1: Sending env LANG = en_US.UTF-8 > debug2: channel 0: request env confirm 0 > debug3: send packet: type 98 > debug3: Ignored env LANGUAGE > debug1: Sending env LC_ADDRESS = pt_BR.UTF-8 > debug2: channel 0: request env confirm 0 > debug3: send packet: type 98 > debug1: Sending env LC_IDENTIFICATION = pt_BR.UTF-8 > debug2: channel 0: request env confirm 0 > debug3: send packet: type 98 > debug1: Sending env LC_MEASUREMENT = pt_BR.UTF-8 > debug2: channel 0: request env confirm 0 > debug3: send packet: type 98 > debug1: Sending env LC_MONETARY = pt_BR.UTF-8 > debug2: channel 0: request env confirm 0 > debug3: send packet: type 98 > debug1: Sending env LC_NAME = pt_BR.UTF-8 > debug2: channel 0: request env confirm 0 > debug3: send packet: type 98 > debug1: Sending env LC_NUMERIC = pt_BR.UTF-8 > debug2: channel 0: request env confirm 0 > debug3: send packet: type 98 > debug1: Sending env LC_PAPER = pt_BR.UTF-8 > debug2: channel 0: request env confirm 0 > debug3: send packet: type 98 > debug1: Sending env LC_TELEPHONE = pt_BR.UTF-8 > debug2: channel 0: request env confirm 0 > debug3: send packet: type 98 > debug1: Sending env LC_TIME = pt_BR.UTF-8 > debug2: channel 0: request env confirm 0 > debug3: send packet: type 98 > debug3: Ignored env LIBVIRT_DEFAULT_URI > debug3: Ignored env LOGNAME > debug3: Ignored env MANDATORY_PATH > debug3: Ignored env PAM_KWALLET5_LOGIN > debug3: Ignored env PAM_KWALLET_LOGIN > debug3: Ignored env PATH > debug3: Ignored env PROFILEHOME > debug3: Ignored env PULSE_PROP_OVERRIDE_application.icon_name > debug3: Ignored env PULSE_PROP_OVERRIDE_application.name > debug3: Ignored env PULSE_PROP_OVERRIDE_application.version > debug3: Ignored env PWD > debug3: Ignored env QT_ACCESSIBILITY > debug3: Ignored env QT_AUTO_SCREEN_SCALE_FACTOR > debug3: Ignored env SESSION_MANAGER > debug3: Ignored env SHELL > debug3: Ignored env SHELL_SESSION_ID > debug3: Ignored env SSH_AGENT_PID > debug3: Ignored env SSH_AUTH_SOCK > debug3: Ignored env TERM > debug3: Ignored env USER > debug3: Ignored env WINDOWID > debug3: Ignored env XAUTHORITY > debug3: Ignored env XCURSOR_THEME > debug3: Ignored env XDG_CONFIG_DIRS > debug3: Ignored env XDG_CURRENT_DESKTOP > debug3: Ignored env XDG_DATA_DIRS > debug3: Ignored env XDG_RUNTIME_DIR > debug3: Ignored env XDG_SEAT > debug3: Ignored env XDG_SEAT_PATH > debug3: Ignored env XDG_SESSION_CLASS > debug3: Ignored env XDG_SESSION_DESKTOP > debug3: Ignored env XDG_SESSION_ID > debug3: Ignored env XDG_SESSION_PATH > debug3: Ignored env XDG_SESSION_TYPE > debug3: Ignored env XDG_VTNR > debug3: Ignored env SHLVL > debug3: Ignored env OLDPWD > debug3: Ignored env GOPATH > debug3: Ignored env ZSH > debug3: Ignored env PAGER > debug3: Ignored env LESS > debug3: Ignored env LSCOLORS > debug3: Ignored env LS_COLORS > debug1: Sending env LC_CTYPE = pt_BR.UTF-8 > debug2: channel 0: request env confirm 0 > debug3: send packet: type 98 > debug3: Ignored env SDKMAN_DIR > debug3: Ignored env SDKMAN_VERSION > debug3: Ignored env SDKMAN_CANDIDATES_API > debug3: Ignored env SDKMAN_PLATFORM > debug3: Ignored env SDKMAN_CANDIDATES_DIR > debug3: Ignored env PERL5LIB > debug3: Ignored env PERL_LOCAL_LIB_ROOT > debug3: Ignored env PERL_MB_OPT > debug3: Ignored env PERL_MM_OPT > debug3: Ignored env _ > debug2: channel 0: request shell confirm 1 > debug3: send packet: type 98 > debug2: channel_input_open_confirmation: channel 0: callback done > debug2: channel 0: open confirm rwindow 0 rmax 32768 > debug3: receive packet: type 99 > debug2: channel_input_status_confirm: type 99 id 0 > debug2: PTY allocation request accepted on channel 0 > debug2: channel 0: rcvd adjust 2097152 > debug3: receive packet: type 99 > debug2: channel_input_status_confirm: type 99 id 0 > debug2: shell request accepted on channel 0 > Last login: Tue Feb 9 09:48:24 UTC 2021 from 10.227.82.104 on pts/0 > > This user is intented to log in only via public key, but packer cannot > connect. Is it possible for packer connect via public key to the guest via > ssh when using the vmware-iso builder or just password ? > > > Em segunda-feira, 8 de fevereiro de 2021 às 16:12:40 UTC-3, > [email protected] escreveu: > >> that's progress.. I would recommend first run the build as follows >> >> *packer build -on-error=ask* * build_file.json* >> >> if you do not find anything "abnormal" , then run packer with *debug >> mode ON * >> On Monday, February 8, 2021 at 2:52:36 PM UTC+1 [email protected] wrote: >> >>> ESXi connection is right, only issue is packer connecting to the guest >>> VM. Checked here and my vm it getting an ipv4, even when I mannually >>> created it. As soon I solve this, I think thr build will run without an >>> issue. >>> >>> Em sexta-feira, 5 de fevereiro de 2021 às 09:50:22 UTC-3, Marc Pires >>> escreveu: >>> >>>> Thanks, I will take a look >>>> >>>> Em quinta-feira, 4 de fevereiro de 2021 às 15:57:54 UTC-3, >>>> [email protected] escreveu: >>>> >>>>> I see you have 2 mote access >>>>> >>>>> 1. to connect to the ESXi >>>>> 2. To connect to the VM once created >>>>> >>>>> Seems your ESXi access is sorted, I did a bit of google and noticed >>>>> the error you are getting, it is likely that is because of a corrupted VM >>>>> Definition >>>>> >>>>> So would recommend you to look first into the definition of your >>>>> vmx_data, In regards this, I did create one a long time ago, you can >>>>> use >>>>> that as a baseline, if helps >>>>> >>>>> https://github.com/macgahe/packer/blob/master/Vm-Template.vmx >>>>> >>>>> But to avoid getting into too much trouble.. will start with a working >>>>> Packer JSON file . CHEF in their github repo have some working templates >>>>> you may want to use as a baseline >>>>> >>>>> https://github.com/chef/bento/tree/master/packer_templates >>>>> >>>>> On Thursday, February 4, 2021 at 2:30:02 PM UTC+1 [email protected] >>>>> wrote: >>>>> >>>>>> But as the VM gets its from DHCP, I will try to set a static ip >>>>>> address for it. Just need to check if I can do it via vmx_data and the >>>>>> correct property to use. (ESXi novice here) >>>>>> >>>>>> On Thu, Feb 4, 2021 at 8:18 AM Marc Pires <[email protected]> wrote: >>>>>> >>>>>>> Checked and packer is connecting to the ESXi not be VM I am >>>>>>> creating, because I have two shell provisioners one to copy a config >>>>>>> file >>>>>>> and the second to set the OS packages. And the config file was copied >>>>>>> to >>>>>>> the ESXi host not the VM. >>>>>>> >>>>>>> >>>>>>> On Thu, Feb 4, 2021 at 7:42 AM Marc Pires <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi Gabo, yes I can login to ESXi using the ssh_password and >>>>>>>> ssh_username values. My password has an @ sign, not sure if it can be >>>>>>>> a >>>>>>>> problem. Checking >>>>>>>> >>>>>>>> On Wed, Feb 3, 2021 at 5:00 PM Gabo Kete <[email protected]> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> looks like you access is being rejected when it tries to ssh into >>>>>>>>> the vmware... can you look into your json file and find the >>>>>>>>> *ssh_username >>>>>>>>> *and* ssh_password entries *and try to logging into your vmware >>>>>>>>> with those values and check if it works >>>>>>>>> >>>>>>>>> On Tuesday, February 2, 2021 at 8:51:13 PM UTC+1 >>>>>>>>> [email protected] wrote: >>>>>>>>> >>>>>>>>>> Hi everyone, I am building an image and during the build I have >>>>>>>>>> the following error below. Any clue of what it can be ? >>>>>>>>>> >>>>>>>>>> 2021/02/02 16:44:57 packer-builder-vmware-iso plugin: [DEBUG] >>>>>>>>>> Opening new ssh session >>>>>>>>>> 2021/02/02 16:44:57 packer-builder-vmware-iso plugin: [DEBUG] >>>>>>>>>> starting remote command: vim-cmd vmsvc/power.on 221 >>>>>>>>>> 2021/02/02 16:44:58 packer-builder-vmware-iso plugin: [ERROR] >>>>>>>>>> Remote command exited with '1': vim-cmd vmsvc/power.on 221 >>>>>>>>>> 2021/02/02 16:45:17 packer-builder-vmware-iso plugin: [DEBUG] >>>>>>>>>> Opening new ssh session >>>>>>>>>> 2021/02/02 16:45:17 packer-builder-vmware-iso plugin: [DEBUG] >>>>>>>>>> starting remote command: vim-cmd vmsvc/power.getstate 221 >>>>>>>>>> 2021/02/02 16:45:18 packer-builder-vmware-iso plugin: [DEBUG] >>>>>>>>>> Opening new ssh session >>>>>>>>>> ==> vmware-iso: Error starting VM: Retry limit exceeded >>>>>>>>>> 2021/02/02 16:45:18 packer-builder-vmware-iso plugin: [DEBUG] >>>>>>>>>> starting remote command: vim-cmd vmsvc/power.getstate 221 >>>>>>>>>> ==> vmware-iso: Destroying virtual machine... >>>>>>>>>> 2021/02/02 16:45:18 packer-builder-vmware-iso plugin: [DEBUG] >>>>>>>>>> Opening new ssh session >>>>>>>>>> 2021/02/02 16:45:18 packer-builder-vmware-iso plugin: [DEBUG] >>>>>>>>>> starting remote command: vim-cmd vmsvc/destroy 221 >>>>>>>>>> 2021/02/02 16:45:19 packer-builder-vmware-iso plugin: [DEBUG] >>>>>>>>>> Opening new ssh session >>>>>>>>>> 2021/02/02 16:45:19 packer-builder-vmware-iso plugin: [DEBUG] >>>>>>>>>> starting remote command: test ! -e >>>>>>>>>> "/vmfs/volumes/DataStorage/Appliance2_dev" >>>>>>>>>> 2021/02/02 16:45:19 packer-builder-vmware-iso plugin: [DEBUG] >>>>>>>>>> Opening new ssh session >>>>>>>>>> 2021/02/02 16:45:19 packer-builder-vmware-iso plugin: [DEBUG] >>>>>>>>>> starting remote command: test -e >>>>>>>>>> "/vmfs/volumes/DataStorage/Appliance2_dev" >>>>>>>>>> 2021/02/02 16:45:19 packer-builder-vmware-iso plugin: [ERROR] >>>>>>>>>> Remote command exited with '1': test -e >>>>>>>>>> "/vmfs/volumes/DataStorage/Appliance2_dev" >>>>>>>>>> 2021/02/02 16:45:19 [INFO] (telemetry) ending vmware-iso >>>>>>>>>> ==> Wait completed after 3 minutes 44 seconds >>>>>>>>>> 2021/02/02 16:45:19 machine readable: error-count []string{"1"} >>>>>>>>>> ==> Some builds didn't complete successfully and had errors: >>>>>>>>>> 2021/02/02 16:45:19 machine readable: vmware-iso,error >>>>>>>>>> []string{"Error starting VM: Retry limit exceeded"} >>>>>>>>>> ==> Builds finished but no artifacts were created. >>>>>>>>>> 2021/02/02 16:45:19 [INFO] (telemetry) Finalizing. >>>>>>>>>> Build 'vmware-iso' errored after 3 minutes 44 seconds: Error >>>>>>>>>> starting VM: Retry limit exceeded >>>>>>>>>> >>>>>>>>> -- >>>>>>>>> This mailing list is governed under the HashiCorp Community >>>>>>>>> Guidelines - https://www.hashicorp.com/community-guidelines.html. >>>>>>>>> Behavior in violation of those guidelines may result in your removal >>>>>>>>> from >>>>>>>>> this mailing list. >>>>>>>>> >>>>>>>>> GitHub Issues: https://github.com/hashicorp/packer/issues >>>>>>>>> IRC: #packer-tool on Freenode >>>>>>>>> --- >>>>>>>>> You received this message because you are subscribed to a topic in >>>>>>>>> the Google Groups "Packer" group. >>>>>>>>> To unsubscribe from this topic, visit >>>>>>>>> https://groups.google.com/d/topic/packer-tool/2UxaWvpjbCs/unsubscribe >>>>>>>>> . >>>>>>>>> To unsubscribe from this group and all its topics, send an email >>>>>>>>> to [email protected]. >>>>>>>>> To view this discussion on the web visit >>>>>>>>> https://groups.google.com/d/msgid/packer-tool/4071302d-8f6b-4cbf-ab0c-f6d5bf0bc842n%40googlegroups.com >>>>>>>>> >>>>>>>>> <https://groups.google.com/d/msgid/packer-tool/4071302d-8f6b-4cbf-ab0c-f6d5bf0bc842n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>>>> . >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Desenvolvedor/DevOps practitioner >>>>>>>> >>>>>>>> https://www.credential.net/5yi8wpmv >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Desenvolvedor/DevOps practitioner >>>>>>> >>>>>>> https://www.credential.net/5yi8wpmv >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Desenvolvedor/DevOps practitioner >>>>>> >>>>>> https://www.credential.net/5yi8wpmv >>>>>> >>>>> -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/hashicorp/packer/issues IRC: #packer-tool on Freenode --- You received this message because you are subscribed to the Google Groups "Packer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/a1d2b901-a067-45b0-aede-2dc3a3a1c95dn%40googlegroups.com.
