Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-8261

[Fiware-lab-help] FIWARE Lab Assistance

        Details

        • Type: extRequest
        • Status: Closed
        • Priority: Major
        • Resolution: Done
        • Fix Version/s: 2021
        • Component/s: FIWARE-LAB-HELP
        • Labels:
          None

          Description

          Hi
          I have a trial account in FiwareLab.

          I have one ubuntu instance that it can be connect to internet and very things in ok on it.

          I have created a ubuntu core lxd container on it. The container have internet connection means ping command is ok but when I execute apt-get update or gwet some url I do get any response.

          Can you help me?

          This is my command

          root@juju-eaeefc-0:~# wget www.google.com
          -2017-02-12 08:12:44- http://www.google.com/
          Resolving www.google.com (www.google.com)... 216.58.214.164, 2a00:1450:4003:801::2004
          Connecting to www.google.com (www.google.com)|216.58.214.164|:80... connected.
          HTTP request sent, awaiting response... 302 Found
          Location: http://www.google.es/?gfe_rd=cr&ei=_RigWNuVA--J8Qealo_oBw [following]
          -2017-02-12 08:12:45- http://www.google.es/?gfe_rd=cr&ei=_RigWNuVA--J8Qealo_oBw
          Resolving www.google.es (www.google.es)... 216.58.214.163, 2a00:1450:4003:801::2003
          Connecting to www.google.es (www.google.es)|216.58.214.163|:80... connected.
          HTTP request sent, awaiting response...
          __________________________________________________________________________________________

          You can get more information about our cookies and privacy policies on the following links:

          Fiware-lab-help mailing list
          Fiware-lab-help@lists.fiware.org
          https://lists.fiware.org/listinfo/fiware-lab-help

          [Created via e-mail received from: Abdoulrahim Sharifi <abdoulrahim@icloud.com>]

            Activity

            Hide
            Permalink
            jicg José Ignacio Carretero Guarde added a comment -

            It may be something related with MTU — As the default mtu for lxc (lxd uses lxc under the hood) is 1500 and the VM's MTU is 1400 there might be some problems.

            The problem should be corrected stablishing the lxc parameter lxc.network.mtu=1400 in /etc/lxc/lxc.conf (for new containers) and in /var/lib/lxc/$

            {CONTAINER_NAME}

            /config for the existing ones. — Althoug it's likely you couldn't have properly configured any container yet.

            Regards,
            José Ignacio

            Show
            jicg José Ignacio Carretero Guarde added a comment - It may be something related with MTU — As the default mtu for lxc (lxd uses lxc under the hood) is 1500 and the VM's MTU is 1400 there might be some problems. The problem should be corrected stablishing the lxc parameter lxc.network.mtu=1400 in /etc/lxc/lxc.conf (for new containers) and in /var/lib/lxc/$ {CONTAINER_NAME} /config for the existing ones. — Althoug it's likely you couldn't have properly configured any container yet. Regards, José Ignacio

              People

              • Assignee:
                jicg José Ignacio Carretero Guarde
                Reporter:
                fw.ext.user FW External User
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: