Is the container used for Magic Jar still a "non-magic object"?

I would like to understand whether the container poured earlier Magic Jar should be considered a magical item and cannot be used for other spells / abilities that require a "non-magical item" such as: B. True polymorph. I would say no because the Sage Advice Compendium (pp. 17-18) lists some criteria that do not match this case, but I am not entirely sure.

Permissions – How do I get permissions to resize the Google Cloud file system in the CoreOS Toolbox container (nspawn / docker)?

TL; DR: To attempt resize2fs /media/root/dev/sdc inside the CoreOS Toolbox container fails, message open: Operation not permitted while opening /media/root/dev/sdc. Probability privilege problem, how do I get the privileges?


I resized a Google Cloud Compute Engine zonal persistent disk from 20 GB to 50 GB. I connected the hard drive to a running VM instance to look around. The change is not shown in the file system df -h after mounting the hard drive, but it does on the device lsblk.

As far as I know, the hard drive has a single file system with no partitions. I have based this mainly on the fact that lsblk No partitions are shown for the device, and I understand that individual file system hard drives are the convention for gcp

Now I've tried resizing the file system by following these documents from Google. However, it was not so easy, since the VMs accessible to me seem to be based on a container-optimized operating system and therefore do not come with the necessary tools or a package manager. So I have to use the CoreOS Toolbox, which, if I understand it correctly, will run a Docker container systemd-nspawn. This gives me access to a package manager and the tools I need.

Toolbox provides the root directory of the host's fs /media/rootSo I can easily access the devices. However, when I tried to use it resize2fs /media/root/dev/sdc According to the above instructions, I get the in the TL; DR mentioned error message. I tried chmod 666 the device inside the VM inside and Toolbox, and it works, but doesn't solve the problem resize2fs. I also tried running Toolbox as root, although I assumed it wouldn't do much. It was not like that. I also unmounted the hard drive before trying one of them.

One solution I imagined would be to run a VM with a more robust operating system image so that I have both "direct" access to the device and direct access to the tools. I am determined to solve the problem with the existing tools as this is more practical in production and I believe that this is possible.

Javascript – When trying to start the Docker container from an error: The virtual machine could not be started because a required function was not installed

Good morning people. Well, I installed the Docker on my computer. however, and I try to configure the Mongo when I try to image the following message: The virtual machine could not be started because a required feature was not installed.

NOTE: I use Windows 10 PRO. Yes, this virtualization is already activated in both the system and the BIOs, and the processor has the virtualization function.

Has anyone had this problem or knows how to solve it? Thank you and bor codar :]

Change the size of the APFS container (encrypted) – ask differently

I have problems with free space that I have on the & # 39; file partition & # 39; available to map to the volume that contains system files: an APFS encrypted container. I want to do this because I can no longer update a large application in the App Store. I've already read some articles dealing with the problem of resizing APFS containers, but they still don't answer my question (or I didn't understand the idea clearly). I run a MacbookAir under Catalina.

I've included some screenshots that may contain more useful information.

Reduce this volume to 90 GBReduce this volume to 90 GB
Increase the capacity of the container to 160 GBIncrease the capacity of the container to 160 GB
discussion listdiscussion list

Thanks for the help guys.

$ form_state => setErrorByName / setError on fieldset / container / etc.

I wrote a custom webform validation handler that compares two fields. If the fields are in a container / field set / etc., I would like to put the error on the container instead of on the fields (since one of the two fields could be the faulty field). For example, the field set is trip dates, the fields are start date and end date and I want an error message if the start date is after the end date.

I can use setErrorByName / setError to set errors for individual fields, but it doesn't work when I try to set an error for the field set. When calling a field set, calling setErrorByName / setError sets the error message at the top of the form, but does nothing to highlight / define an error class in the field set.

Webform source:

event_details:
  '#type': fieldset
  '#title': 'Event Details'
  '#attributes':
     name: event-details
  date_container:
    '#type': fieldset
    '#title': 'Travel Dates'
    '#required': true
    '#attributes':
       name: date-container
     departure_date:
       '#type': date
       '#title': 'Departure Date'
       '#required': true
       '#default_value': '+1 day'
       '#format': short
       '#date_date_min': today
       '#datepicker': true
       '#datepicker_button': true
       '#date_date_format': m/d/Y
     return_date:
       '#type': date
       '#title': 'Return Date'
       '#required': true
       '#default_value': '+1 day'
       '#format': short
       '#date_date_min': today
       '#datepicker': true
       '#datepicker_button': true
       '#date_date_format': m/d/Y

Class code:

  $errorFields=(
     'date_container',  //sets message, fails to highlight
     'date-container',  //sets message, fails to highlight
     'event_details)(date_container',   //sets message, fails to highlight
     'event-details)(date-container',   //sets message, fails to highlight
     'return-date',     //sets message, fails to highlight, as expected
     'departure-date',  //sets message, fails to highlight, as expected
     'return_date',     //sets message, highlights single field as expected
     'departure_date',  //sets message, highlights single field as expected
  );
  foreach($errorsField as $errorField){
    if (!($left_val <= $right_val)) {
      $formState->setErrorByName(
       $errorField,
      $this->t('some weird message'));
    }
  }

I also tried changing the container names to underscores instead of hyphens … no luck. If it only added an error class to the field set, I could format it easily enough, but it doesn't seem to change the field set.

I also tried container, details and section instead of fieldset.

ubuntu – Postgresql as Docker container that does not start with the start data of the assigned volume

On my MacBook, Postgres runs in a Docker container and I use a mapped volume to store the data. This works perfectly on site.

However, when I try to do the same on an Ubuntu server, the & # 39; initial & # 39; No data from the mapped volume. Postgres starts in an & # 39; empty & # 39; Initial state.
I can see that disk mapping is working and I have checked and confirmed the Postgres data folder in the container.
Interestingly, the mapping seems to work because an added table and data in that table are persistent in the standard Postgres database. It is also interesting to note that when trying to create a table in a new database, an error message is displayed. The new database is also persistent, but the table cannot be saved because of an error:

File "base / 16384/2611" could not be opened: No such file or directory

This is expected because the base / 16384 folder does not exist.

To me, does this seem to be a user / rights issue or a Postgres setting? I tried to run the container as root, which didn't help.

Any suggestions?

I start the container either with Docker-Compose or via the command line;

docker run --rm --name pg -e POSTGRES_PASSWORD=[password] -d -p 5432:5432 -v /ro

Can different darkroom chemicals be disposed of in the same container?

I am an absolute ignorant of chemistry, but from time to time I like to process my own (black and white) films in an ex-Tempore darkroom (read: the bathroom). I understand that the correct way to dispose of darkroom chemicals is to store used chemicals until you have accumulated enough to take them to the local hazardous waste processing facility. That is, not down the drain.

I have two questions:

  1. Can different "classes" of chemicals – developer, stop bath, fixer, possibly bleach and toner – get in the same container? I assume "no", but I would like to hear why.
  2. Can different "copies" in the same "class" go in the same container? I am particularly curious about developers here, since you are probably experimenting with several and therefore have several different exhausted developers at your disposal. Are there known interactions between common development agents that could make the preparation more harmful or downright dangerous?

Ubuntu – running a self-hosted GitLab CE / EE in a Docker container: how effective and / or popular? [NOT Docker for GitLab Runner]

How many users / communities execute GitLab CE / EE for production in a Docker image / container? In other words, how popular, effective and reliable does GitLabCE / EE run on / in Docker? My team is trying to measure the maturity of the GitLabCE / CE-in-Docker use case based on its popularity.

(This is a VERY DIFFERENT item / a VERY DIFFERENT question than the question about GitLab runners in Docker for CI / CD purposes. I am asking for the actual GitLab CE / EE core server.)

We see the following guide, which seems very helpful: https://docs.gitlab.com/omnibus/docker/

More details

My team is considering running GitLab CE / EE in a Docker Compose configuration on an Ubuntu host server that includes FreeIPA, Antora, Postfix, Dovecot, and other server apps, with each server app (possibly, probably?) As Docker- Image is saved. runs as a Docker container.

centos – Solr, which runs on a Docker container, uses localhost, but not the container IP

I used Docker Hub's official CentOS 7 image and created a container to run Solr 8.4.1 Execution. I was able to start and run the Solr without any problems. My concern is, Solr Admin UI loads with localhost URL (http: // localhost: 7574 / solr /), but not with the assigned IP for the container (http://172.18.0.6:7574/solr/).

/ etc / hosts The file in the container looks like this.

(solr@solrtwo solr-8.4.1)$ cat /etc/hosts
127.0.0.1   localhost
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
172.18.0.6  solrtwo

I have also activated the following line solr.in.sh also

SOLR_HOST="172.18.0.6"

In addition, the result for the Docker inspection for the container is as follows.

    "NetworkSettings": {
        "Bridge": "",
        "SandboxID": "87cf51134d0b4bc3068ab8e294f5dc91bfc2db79528064002135beaa6c84b074",
        "HairpinMode": false,
        "LinkLocalIPv6Address": "",
        "LinkLocalIPv6PrefixLen": 0,
        "Ports": {
            "7574/tcp": (
                {
                    "HostIp": "0.0.0.0",
                    "HostPort": "7574"
                }
            )
        },
        "SandboxKey": "/var/run/docker/netns/87cf51134d0b",
        "SecondaryIPAddresses": null,
        "SecondaryIPv6Addresses": null,
        "EndpointID": "",
        "Gateway": "",
        "GlobalIPv6Address": "",
        "GlobalIPv6PrefixLen": 0,
        "IPAddress": "",
        "IPPrefixLen": 0,
        "IPv6Gateway": "",
        "MacAddress": "",
        "Networks": {
            "zone1": {
                "IPAMConfig": null,
                "Links": null,
                "Aliases": (
                    "095f310ec70f"
                ),
                "NetworkID": "c9ab125d4c36228a46447514f0e13867bff50607c6c1e4b726172b5c3393a9fb",
                "EndpointID": "19a143b947bab68fe058e87f130bd1dd2e3b89b32c27d826c9ee4b3b55d30474",
                "Gateway": "172.18.0.1",
                "IPAddress": "172.18.0.6",
                "IPPrefixLen": 16,
                "IPv6Gateway": "",
                "GlobalIPv6Address": "",
                "GlobalIPv6PrefixLen": 0,
                "MacAddress": "02:42:ac:12:00:06",
                "DriverOpts": null
            }
        }
    }

I want to load the Solr administrator user interface with the container IP address instead of localhost. How can I do that?