How to set up working uid/gid allocations for LXC/LXD/Vagrant?Vagrant-lxc container not startingWhat is the difference between Docker, LXD, and LXCHow do I make changes to an lxc template?Uid/Gid privileged LXC container : systemd lxc-start failed on ubuntu 16.04Running a program inside an LXC container with a specific userHow to boot a virtual machine from a regular folder?How to manage users and passwords in LXC containers?How to implement iptables on lxc-container?How to trust self-signed LXD daemon TLS certificate in Vagrant?What to put in /etc/subu,gid to run unprivileged containers?

Is it appropriate to ask a former professor to order a library book for me through ILL?

School performs periodic password audits. Is my password compromised?

Tool for measuring readability of English text

Should I apply for my boss's promotion?

Why does a car's steering wheel get lighter with increasing speed

Short story about an infectious indestructible metal bar?

Is there a math expression equivalent to the conditional ternary operator?

How to make sure I'm assertive enough in contact with subordinates?

How does learning spells work when leveling a multiclass character?

I am the person who abides by rules but breaks the rules . Who am I

What is the oldest European royal house?

How does a sound wave propagate?

I am the light that shines in the dark

Is this Paypal Github SDK reference really a dangerous site?

What does *dead* mean in *What do you mean, dead?*?

Interpretation of linear regression interaction term plot

What does it take to become a wilderness skills guide as a business?

Why do phishing e-mails use faked e-mail addresses instead of the real one?

Did Amazon pay $0 in taxes last year?

Boss Telling direct supervisor I snitched

A vote on the Brexit backstop

What exactly is the meaning of "fine wine"?

Does an unused member variable take up memory?

Professor forcing me to attend a conference, I can't afford even with 50% funding



How to set up working uid/gid allocations for LXC/LXD/Vagrant?


Vagrant-lxc container not startingWhat is the difference between Docker, LXD, and LXCHow do I make changes to an lxc template?Uid/Gid privileged LXC container : systemd lxc-start failed on ubuntu 16.04Running a program inside an LXC container with a specific userHow to boot a virtual machine from a regular folder?How to manage users and passwords in LXC containers?How to implement iptables on lxc-container?How to trust self-signed LXD daemon TLS certificate in Vagrant?What to put in /etc/subu,gid to run unprivileged containers?













0















What I've tried:



$ vagrant up --no-provision
Bringing machine 'default' up with 'lxd' provider...
==> default: Machine has not been created yet, starting...
==> default: The host machine does not support LXD synced folders.
==> default:
==> default: To use this feature, you must first configure ID mappings for the
==> default: current user in /etc/subuid and /etc/subgid. For more information,
==> default: refer to `vagrant lxd shadow --help`.
==> default:
==> default: Importing LXC image...
[fails]


OK, let's try the advice:



$ vagrant lxd shadow --help
In order to use shared folders, you must first add the effective user
and group ID (which are currently 1000 and 985) to the host machine's
subuid(5) and subgid(5) files:

$ echo root:1000:1 | sudo tee -a /etc/subuid
$ echo root:985:1 | sudo tee -a /etc/subgid

For more information about these commands, and user/group ID mapping in
general, refer to this article:

https://insights.ubuntu.com/2017/06/15/custom-user-mappings-in-lxd-containers/
$ echo root:1000:1 | sudo tee -a /etc/subuid
root:1000:1
$ echo root:985:1 | sudo tee -a /etc/subgid
root:985:1
$ vagrant up --no-provision
Bringing machine 'default' up with 'lxd' provider...
==> default: Machine has not been created yet, starting...
==> default: Importing LXC image...
==> default: Failed to create container
The provider was unable to create a container for the 'default' VM.

The underlying error message was: Create container: Create LXC container: LXD doesn't have a uid/gid allocation. In this mode, only privileged containers are supported

The LXD logs may contain more information about the cause of this failure.


OK, I'm getting desperate. Let's try a bunch of suggestions from all over the place (1, 2, 3). No luck. In all cases I get one of the two above messages. The messages are also weird, because to me they look like they mean the exact same thing, so I don't know which of the solutions get "further" than the other. Especially since the advice all over the place for both messages seem to be the same thing I've tried a dozen times by now, including at least:



  • printf "%s:100000:65536n" lxd root | sudo tee /etc/subgid /etc/subuid

  • printf "%s:1:65536n" lxd root | sudo tee /etc/subgid /etc/subuid

  • printf "%s:1:65536n" root vagrant $USER | sudo tee /etc/subgid /etc/subuid

I've made sure to sudo systemctl restart lxd before every vagrant up.




printf "%s:1000:65536n" lxd root | sudo tee /etc/subuid && printf "%s:985:65536n" lxd root | sudo tee /etc/subgid gave me an interestingly different error message:




Create LXC container: Host id is in the range of subids




No idea why that is an error or how to fix it.




In case it's relevant, the vagrant user on the box is UID/GID 1000/1000 (after starting it with VirtualBox).










share|improve this question




























    0















    What I've tried:



    $ vagrant up --no-provision
    Bringing machine 'default' up with 'lxd' provider...
    ==> default: Machine has not been created yet, starting...
    ==> default: The host machine does not support LXD synced folders.
    ==> default:
    ==> default: To use this feature, you must first configure ID mappings for the
    ==> default: current user in /etc/subuid and /etc/subgid. For more information,
    ==> default: refer to `vagrant lxd shadow --help`.
    ==> default:
    ==> default: Importing LXC image...
    [fails]


    OK, let's try the advice:



    $ vagrant lxd shadow --help
    In order to use shared folders, you must first add the effective user
    and group ID (which are currently 1000 and 985) to the host machine's
    subuid(5) and subgid(5) files:

    $ echo root:1000:1 | sudo tee -a /etc/subuid
    $ echo root:985:1 | sudo tee -a /etc/subgid

    For more information about these commands, and user/group ID mapping in
    general, refer to this article:

    https://insights.ubuntu.com/2017/06/15/custom-user-mappings-in-lxd-containers/
    $ echo root:1000:1 | sudo tee -a /etc/subuid
    root:1000:1
    $ echo root:985:1 | sudo tee -a /etc/subgid
    root:985:1
    $ vagrant up --no-provision
    Bringing machine 'default' up with 'lxd' provider...
    ==> default: Machine has not been created yet, starting...
    ==> default: Importing LXC image...
    ==> default: Failed to create container
    The provider was unable to create a container for the 'default' VM.

    The underlying error message was: Create container: Create LXC container: LXD doesn't have a uid/gid allocation. In this mode, only privileged containers are supported

    The LXD logs may contain more information about the cause of this failure.


    OK, I'm getting desperate. Let's try a bunch of suggestions from all over the place (1, 2, 3). No luck. In all cases I get one of the two above messages. The messages are also weird, because to me they look like they mean the exact same thing, so I don't know which of the solutions get "further" than the other. Especially since the advice all over the place for both messages seem to be the same thing I've tried a dozen times by now, including at least:



    • printf "%s:100000:65536n" lxd root | sudo tee /etc/subgid /etc/subuid

    • printf "%s:1:65536n" lxd root | sudo tee /etc/subgid /etc/subuid

    • printf "%s:1:65536n" root vagrant $USER | sudo tee /etc/subgid /etc/subuid

    I've made sure to sudo systemctl restart lxd before every vagrant up.




    printf "%s:1000:65536n" lxd root | sudo tee /etc/subuid && printf "%s:985:65536n" lxd root | sudo tee /etc/subgid gave me an interestingly different error message:




    Create LXC container: Host id is in the range of subids




    No idea why that is an error or how to fix it.




    In case it's relevant, the vagrant user on the box is UID/GID 1000/1000 (after starting it with VirtualBox).










    share|improve this question


























      0












      0








      0








      What I've tried:



      $ vagrant up --no-provision
      Bringing machine 'default' up with 'lxd' provider...
      ==> default: Machine has not been created yet, starting...
      ==> default: The host machine does not support LXD synced folders.
      ==> default:
      ==> default: To use this feature, you must first configure ID mappings for the
      ==> default: current user in /etc/subuid and /etc/subgid. For more information,
      ==> default: refer to `vagrant lxd shadow --help`.
      ==> default:
      ==> default: Importing LXC image...
      [fails]


      OK, let's try the advice:



      $ vagrant lxd shadow --help
      In order to use shared folders, you must first add the effective user
      and group ID (which are currently 1000 and 985) to the host machine's
      subuid(5) and subgid(5) files:

      $ echo root:1000:1 | sudo tee -a /etc/subuid
      $ echo root:985:1 | sudo tee -a /etc/subgid

      For more information about these commands, and user/group ID mapping in
      general, refer to this article:

      https://insights.ubuntu.com/2017/06/15/custom-user-mappings-in-lxd-containers/
      $ echo root:1000:1 | sudo tee -a /etc/subuid
      root:1000:1
      $ echo root:985:1 | sudo tee -a /etc/subgid
      root:985:1
      $ vagrant up --no-provision
      Bringing machine 'default' up with 'lxd' provider...
      ==> default: Machine has not been created yet, starting...
      ==> default: Importing LXC image...
      ==> default: Failed to create container
      The provider was unable to create a container for the 'default' VM.

      The underlying error message was: Create container: Create LXC container: LXD doesn't have a uid/gid allocation. In this mode, only privileged containers are supported

      The LXD logs may contain more information about the cause of this failure.


      OK, I'm getting desperate. Let's try a bunch of suggestions from all over the place (1, 2, 3). No luck. In all cases I get one of the two above messages. The messages are also weird, because to me they look like they mean the exact same thing, so I don't know which of the solutions get "further" than the other. Especially since the advice all over the place for both messages seem to be the same thing I've tried a dozen times by now, including at least:



      • printf "%s:100000:65536n" lxd root | sudo tee /etc/subgid /etc/subuid

      • printf "%s:1:65536n" lxd root | sudo tee /etc/subgid /etc/subuid

      • printf "%s:1:65536n" root vagrant $USER | sudo tee /etc/subgid /etc/subuid

      I've made sure to sudo systemctl restart lxd before every vagrant up.




      printf "%s:1000:65536n" lxd root | sudo tee /etc/subuid && printf "%s:985:65536n" lxd root | sudo tee /etc/subgid gave me an interestingly different error message:




      Create LXC container: Host id is in the range of subids




      No idea why that is an error or how to fix it.




      In case it's relevant, the vagrant user on the box is UID/GID 1000/1000 (after starting it with VirtualBox).










      share|improve this question
















      What I've tried:



      $ vagrant up --no-provision
      Bringing machine 'default' up with 'lxd' provider...
      ==> default: Machine has not been created yet, starting...
      ==> default: The host machine does not support LXD synced folders.
      ==> default:
      ==> default: To use this feature, you must first configure ID mappings for the
      ==> default: current user in /etc/subuid and /etc/subgid. For more information,
      ==> default: refer to `vagrant lxd shadow --help`.
      ==> default:
      ==> default: Importing LXC image...
      [fails]


      OK, let's try the advice:



      $ vagrant lxd shadow --help
      In order to use shared folders, you must first add the effective user
      and group ID (which are currently 1000 and 985) to the host machine's
      subuid(5) and subgid(5) files:

      $ echo root:1000:1 | sudo tee -a /etc/subuid
      $ echo root:985:1 | sudo tee -a /etc/subgid

      For more information about these commands, and user/group ID mapping in
      general, refer to this article:

      https://insights.ubuntu.com/2017/06/15/custom-user-mappings-in-lxd-containers/
      $ echo root:1000:1 | sudo tee -a /etc/subuid
      root:1000:1
      $ echo root:985:1 | sudo tee -a /etc/subgid
      root:985:1
      $ vagrant up --no-provision
      Bringing machine 'default' up with 'lxd' provider...
      ==> default: Machine has not been created yet, starting...
      ==> default: Importing LXC image...
      ==> default: Failed to create container
      The provider was unable to create a container for the 'default' VM.

      The underlying error message was: Create container: Create LXC container: LXD doesn't have a uid/gid allocation. In this mode, only privileged containers are supported

      The LXD logs may contain more information about the cause of this failure.


      OK, I'm getting desperate. Let's try a bunch of suggestions from all over the place (1, 2, 3). No luck. In all cases I get one of the two above messages. The messages are also weird, because to me they look like they mean the exact same thing, so I don't know which of the solutions get "further" than the other. Especially since the advice all over the place for both messages seem to be the same thing I've tried a dozen times by now, including at least:



      • printf "%s:100000:65536n" lxd root | sudo tee /etc/subgid /etc/subuid

      • printf "%s:1:65536n" lxd root | sudo tee /etc/subgid /etc/subuid

      • printf "%s:1:65536n" root vagrant $USER | sudo tee /etc/subgid /etc/subuid

      I've made sure to sudo systemctl restart lxd before every vagrant up.




      printf "%s:1000:65536n" lxd root | sudo tee /etc/subuid && printf "%s:985:65536n" lxd root | sudo tee /etc/subgid gave me an interestingly different error message:




      Create LXC container: Host id is in the range of subids




      No idea why that is an error or how to fix it.




      In case it's relevant, the vagrant user on the box is UID/GID 1000/1000 (after starting it with VirtualBox).







      lxc vagrant lxd vagrant-lxd






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 5 hours ago







      l0b0

















      asked 5 hours ago









      l0b0l0b0

      28.4k19120248




      28.4k19120248




















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "106"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader:
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          ,
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













          draft saved

          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f505227%2fhow-to-set-up-working-uid-gid-allocations-for-lxc-lxd-vagrant%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f505227%2fhow-to-set-up-working-uid-gid-allocations-for-lxc-lxd-vagrant%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Frič See also Navigation menuinternal link

          Identify plant with long narrow paired leaves and reddish stems Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?What is this plant with long sharp leaves? Is it a weed?What is this 3ft high, stalky plant, with mid sized narrow leaves?What is this young shrub with opposite ovate, crenate leaves and reddish stems?What is this plant with large broad serrated leaves?Identify this upright branching weed with long leaves and reddish stemsPlease help me identify this bulbous plant with long, broad leaves and white flowersWhat is this small annual with narrow gray/green leaves and rust colored daisy-type flowers?What is this chilli plant?Does anyone know what type of chilli plant this is?Help identify this plant

          fontconfig warning: “/etc/fonts/fonts.conf”, line 100: unknown “element blank” The 2019 Stack Overflow Developer Survey Results Are In“tar: unrecognized option --warning” during 'apt-get install'How to fix Fontconfig errorHow do I figure out which font file is chosen for a system generic font alias?Why are some apt-get-installed fonts being ignored by fc-list, xfontsel, etc?Reload settings in /etc/fonts/conf.dTaking 30 seconds longer to boot after upgrade from jessie to stretchHow to match multiple font names with a single <match> element?Adding a custom font to fontconfigRemoving fonts from fontconfig <match> resultsBroken fonts after upgrading Firefox ESR to latest Firefox