Getting below error while updating drupal core to 8.2.4 from 8.2.8
Fatal error: Declaration of Drupal\Component\DependencyInjection\Container::set($id, $service) must be compatible with Symfony\Component\DependencyInjection\ContainerInterface::set($id, $service, $scope = self::SCOPE_CONTAINER) in C:\inetpub\wwwroot\drupal-8\ihlocal\docroot\core\lib\Drupal\Component\DependencyInjection\Container.php on line 47

Any help

Comments

poonam11210 created an issue. See original summary.

cilefen’s picture

cilefen commented
Title: Getting fatel error while updating drupal core to 8.2.4 from 8.2.8 » Getting fatal error while updating drupal core to 8.2.4 from 8.2.8
Component: configuration system » base system
Issue tags: -drupal core, -FAtel error +Needs steps to reproduce

What was the upgrade process on this site? Are you using drush?

poonam11210’s picture

poonam11210 commented

No I dont have drush. i am trying manually and using composer also

cilefen’s picture

cilefen commented

We don’t know what you did because you haven’t told us so to provide help will be difficult. Incidentally there is no longer support for 8.2.x versions.

poonam11210’s picture

poonam11210 commented

After updating I am getting error like
Fatal error: Uncaught Error: Class 'Drupal\Core\DrupalKernel' not found in \index.php:19 Stack trace: #0 {main} thrown in \index.php on line 19
Any suggestion for this?

poonam11210’s picture

poonam11210 commented
Title: Getting fatal error while updating drupal core to 8.2.4 from 8.2.8 » Getting fatal error while updating drupal core to 8.2.4 from 8.4.2/8.4.3
cilefen’s picture

cilefen commented

You have not yet described how you upgraded.

tdebruyn’s picture

tdebruyn commented

Sorry for highjacking this thread, I initially thought I had a very similar problem but after further testing, it appears that the problem is linked to PHP 7.2, downgrading back to PHP 7.1.12 solved my problem. PHP 7.2 is not yet supported with Drupal 8.

hgoto’s picture

hgoto commented

I met this problem after updating the core from 8.3.x to 8.4.x.

My steps to update the core are:

1. Run drush up drupal.
2. Access the page or try to use drush php.

Only that.

In my case, it seems that the problem is caused since I updated only files under core/ (Drupal\Component\DependencyInjection\Container is included) and left files under vendor/ (Symfony\Component\DependencyInjection\ContainerInterface is included). The signature of Symfony\Component\DependencyInjection\ContainerInterface::set() changed between 8.3.x and 8.4.x and the mismatch of the interface occurred.

8.3.x
https://api.drupal.org/api/drupal/vendor%21symfony%21dependency-injectio...

8.4.x
https://api.drupal.org/api/drupal/vendor%21symfony%21dependency-injectio...

In my case, the error has gone after updating the files under vendor/ by running the command composer install in the root directory.

hgoto’s picture

hgoto commented
Related issues: +#2914881: Upgrade from 8.3.7 to 8.4.0 results in fatal "Drupal\Component\DependencyInjection\Container::set() must be compatible with Symfony\Component\DependencyInjection\ContainerInterface::set()"

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

pameeela’s picture

pameeela commented
Status: Active » Closed (works as designed)

Thanks for reporting this issue. We rely on issue reports like this one to resolve bugs and improve Drupal core.

As part of the Bug Smash Initiative, we are triaging issues that are marked “Needs steps to reproduce“.

Since there were no specific steps provided by the original reporter, and hgoto has posted some tips on how to resolve this in #9 , I'm marking the issue "Closed (works as designed)".

Thanks!

pameeela’s picture

pameeela commented
Issue tags: +Bug Smash Initiative